[
https://issues.apache.org/jira/browse/ARTEMIS-2240?focusedWorklogId=212546&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-212546
]
ASF GitHub Bot logged work on ARTEMIS-2240:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/19 17:37
Start Date: 13/Mar/19 17:37
Worklog Time Spent: 10m
Work Description: franz1981 commented on issue #2582: Revert
"ARTEMIS-2240 ActiveMQThreadPoolExecutor should use LinkedTransferQueue"
URL: https://github.com/apache/activemq-artemis/pull/2582#issuecomment-472528765
@michaelandrepearce
I have added them for a specific reason :)
The 2.6.4 tag was my original baseline, while
7dfa0fe7f43012f2f4ee5715049878019fe0bef7 was my original bet about the reason
of the regression and 71d549434591715c1f02359000e424e4d7dfbfda was the commit
right before it (that I have used to validate that
7dfa0fe7f43012f2f4ee5715049878019fe0bef7 wasn't guilty of anything).
I have already tried the commit that has introduced the new thread pool too
vs reverting it and master vs this PR too: my box always report the new thread
pool as the source of the latency regression.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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: 212546)
Time Spent: 5.5h (was: 5h 20m)
> ActiveMQThreadPoolExecutor should use LinkedTransferQueue
> ---------------------------------------------------------
>
> Key: ARTEMIS-2240
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2240
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> ActiveMQThreadPoolExecutor should use LinkedTransferQueue to reduce cost over
> contention, given that internally it isn't using ReentrantLock as
> LinkedBlockingQueue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
