[ 
https://issues.apache.org/jira/browse/ARTEMIS-2236?focusedWorklogId=188708&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-188708
 ]

ASF GitHub Bot logged work on ARTEMIS-2236:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Jan/19 08:29
            Start Date: 23/Jan/19 08:29
    Worklog Time Spent: 10m 
      Work Description: michaelandrepearce commented on issue #2514: 
ARTEMIS-2236 Address Latency Impact caused by ARTEMIS-1451
URL: https://github.com/apache/activemq-artemis/pull/2514#issuecomment-456712653
 
 
   @franz1981 we dont even need, that the % change is quite significant. 
   
   Also note 
https://github.com/apache/activemq-artemis/pull/1577/commits/f8b758d14bc4dac7d613e1d15a65d31289f0a587
 seems got merged very quickly without much perf critique. Flew under the radar 
so to say. (took a while for us to find the cause of the latency decrease since 
upgrade because of this!)
   
   This is simply reverting that, and addressing the sync concerns in the 
original version.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 188708)
    Time Spent: 2.5h  (was: 2h 20m)

> Address Latency Impact caused by ARTEMIS-1451
> ---------------------------------------------
>
>                 Key: ARTEMIS-2236
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2236
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.4.0, 2.5.0, 2.6.0
>            Reporter: Michael Andre Pearce
>            Priority: Blocker
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> h1. ARTEMIS-1451 whilst may have removed syncronisation, increased latency as 
> the overhead of creating a new thread vs re-using an idle one is significant. 
> It is the main reason of a thread pool.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to