[
https://issues.apache.org/jira/browse/ARTEMIS-2236?focusedWorklogId=188713&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-188713
]
ASF GitHub Bot logged work on ARTEMIS-2236:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/19 08:33
Start Date: 23/Jan/19 08:33
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-456714410
@michaelandrepearce I do understand but I believe that it could be dependent
by a wrong configuration, given that the behaviour of the thread-pool is quite
different from before: did you have tried to change the configuration of the
thread-pool according to this new behaviour?
----------------------------------------------------------------
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: 188713)
Time Spent: 3h (was: 2h 50m)
> 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: 3h
> 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)
