You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/23 08:10:00 UTC
[jira] [Work logged] (ARTEMIS-2236) Address Latency Impact caused
by ARTEMIS-1451
[ https://issues.apache.org/jira/browse/ARTEMIS-2236?focusedWorklogId=188688&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-188688 ]
ASF GitHub Bot logged work on ARTEMIS-2236:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/19 08:09
Start Date: 23/Jan/19 08:09
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on pull request #2514: ARTEMIS-2236 Address Latency Impact caused by ARTEMIS-1451
URL: https://github.com/apache/activemq-artemis/pull/2514
Revert ARTEMIS-1451
Remove synchronization by simplifying original code and using atomics
----------------------------------------------------------------
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 188688)
Time Spent: 10m
Remaining Estimate: 0h
> 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: 10m
> 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)