[
https://issues.apache.org/jira/browse/ARTEMIS-2236?focusedWorklogId=188746&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-188746
]
ASF GitHub Bot logged work on ARTEMIS-2236:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/19 09:02
Start Date: 23/Jan/19 09:02
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2514:
ARTEMIS-2236 Address Latency Impact caused by ARTEMIS-1451
URL: https://github.com/apache/activemq-artemis/pull/2514#issuecomment-456722769
So all ive done, is revert that change of 1451 to put back semantics.
Streamlined the code a tad, so then we can remove sync blocks, and can just
make the updating of threadTaskDelta using an atomic updater rather than doing
it inside a sync block. Which then re-addresses concern of 1451 which was sync
blocks.
----------------------------------------------------------------
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: 188746)
Time Spent: 6h 50m (was: 6h 40m)
> 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: 6h 50m
> 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)
