[
https://issues.apache.org/jira/browse/ARTEMIS-2236?focusedWorklogId=188733&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-188733
]
ASF GitHub Bot logged work on ARTEMIS-2236:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/19 08:51
Start Date: 23/Jan/19 08:51
Worklog Time Spent: 10m
Work Description: franz1981 commented on issue #2514: ARTEMIS-2236
Address Latency Impact caused by ARTEMIS-1451
URL: https://github.com/apache/activemq-artemis/pull/2514#issuecomment-456719095
@michaelandrepearce
Ok and the old thread-pool, assuming max thread count already reached, was
equally distributing the load across threads?
> roughly correct
If I've missed anything, please correct me, it helps me to understand ;)
----------------------------------------------------------------
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: 188733)
Time Spent: 5.5h (was: 5h 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: 5.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)
