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

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

                Author: ASF GitHub Bot
            Created on: 23/Jan/19 08:21
            Start Date: 23/Jan/19 08:21
    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-456708382
 
 
   1451 removed synchronization in the class, by adding the overhead of 
creating a new thread until threadpool is full, this though means that instead 
of re-using an idle thread for new work, new threads are being created which is 
expensive, and the point of thread pooling.
   
   We have seen a 15-20% latency increase hit due to this.
 
----------------------------------------------------------------
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: 188697)
    Time Spent: 1h 10m  (was: 1h)

> 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: 1h 10m
>  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