[
https://issues.apache.org/jira/browse/ARTEMIS-2240?focusedWorklogId=212549&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-212549
]
ASF GitHub Bot logged work on ARTEMIS-2240:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/19 17:39
Start Date: 13/Mar/19 17:39
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2582: Revert
"ARTEMIS-2240 ActiveMQThreadPoolExecutor should use LinkedTransferQueue"
URL: https://github.com/apache/activemq-artemis/pull/2582#issuecomment-472529670
So where is this putting us back to. My original ? Or the version we had
perf issue with?
----------------------------------------------------------------
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: 212549)
Time Spent: 5h 50m (was: 5h 40m)
> 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: 5h 50m
> 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)
