[
https://issues.apache.org/jira/browse/ARTEMIS-2240?focusedWorklogId=190481&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-190481
]
ASF GitHub Bot logged work on ARTEMIS-2240:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 27/Jan/19 02:44
Start Date: 27/Jan/19 02:44
Worklog Time Spent: 10m
Work Description: franz1981 commented on issue #2524: ARTEMIS-2240
ActiveMQThreadPoolExecutor should use LinkedTransferQueue
URL: https://github.com/apache/activemq-artemis/pull/2524#issuecomment-457884054
On my box I'm getting the same performance of the master version for single
producer/single consumer workloads and a better scalability with 8 producers/8
consumers (on different queues) for both the commits I've attached (the second
one, in particular).
I'm putting this for review and for validation: if anyone has a better
machine to validate its behaviour is wellcome.
A conservative approach will suggest to just use the first commit ie a
simple q replacement, but I the second commit has more to offer given that
would allow to use what this q offer out of the box and that seems very similar
to what the thread pool was delivering in the implementation on master.
----------------------------------------------------------------
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: 190481)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
