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/10 15:41:00 UTC
[jira] [Work logged] (ARTEMIS-2205) Make AMQP Processing Single
Threaded and other AMQP perf improvements
[ https://issues.apache.org/jira/browse/ARTEMIS-2205?focusedWorklogId=183751&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-183751 ]
ASF GitHub Bot logged work on ARTEMIS-2205:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 10/Jan/19 15:40
Start Date: 10/Jan/19 15:40
Worklog Time Spent: 10m
Work Description: asfgit commented on pull request #2467: ARTEMIS-2205 Performance improvements on AMQP and other parts
URL: https://github.com/apache/activemq-artemis/pull/2467
----------------------------------------------------------------
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: 183751)
Time Spent: 10m
Remaining Estimate: 0h
> Make AMQP Processing Single Threaded and other AMQP perf improvements
> ---------------------------------------------------------------------
>
> Key: ARTEMIS-2205
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2205
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: AMQP
> Affects Versions: 2.6.3
> Reporter: clebert suconic
> Assignee: clebert suconic
> Priority: Major
> Fix For: 2.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is using Netty Executor (NIOLoop) to process AMQP.
> Instead of using a lock to enter the AMQP processing, what has issues on scaling up multiple connections per queue, it's using a single threaded executor.
>
>
> This represents a major improvement in AMQP. I will take my time to write a blog post about this with multiple scenarios comparing 2.6.3, master (before this change) and after. (I will post a link here to this JIRA).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)