[
https://issues.apache.org/jira/browse/ARTEMIS-2236?focusedWorklogId=188776&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-188776
]
ASF GitHub Bot logged work on ARTEMIS-2236:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/19 09:39
Start Date: 23/Jan/19 09:39
Worklog Time Spent: 10m
Work Description: gemmellr commented on issue #2514: ARTEMIS-2236 Address
Latency Impact caused by ARTEMIS-1451
URL: https://github.com/apache/activemq-artemis/pull/2514#issuecomment-456734370
Franz is the man for this type of thing so I'll leave him to the review, but
I do think having a separate specific revert commit would have actually been a
good idea given it looks to change so much, making it easier for someone
looking at 'actual changes' from the original to do so easily. Essentially, in
general I think if its worth actually reverting something, do that specifically.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 188776)
Time Spent: 10.5h (was: 10h 20m)
> 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: 10.5h
> 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)
