You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/04/13 02:57:00 UTC
[jira] [Resolved] (JAMES-3041) RabbitMQ dequeue is not using the
spooler threadpool
[ https://issues.apache.org/jira/browse/JAMES-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier resolved JAMES-3041.
-----------------------------------
Fix Version/s: 3.6.0
Resolution: Fixed
https://github.com/linagora/james-project/pull/3137 is contributing this
> RabbitMQ dequeue is not using the spooler threadpool
> ----------------------------------------------------
>
> Key: JAMES-3041
> URL: https://issues.apache.org/jira/browse/JAMES-3041
> Project: James Server
> Issue Type: Bug
> Components: rabbitmq
> Reporter: Matthieu Baechler
> Priority: Major
> Fix For: 3.6.0
>
>
> In recent load tests, while trying to understand why object storage backend is making mail dequeuing slow, we found that RabbitMQ Mailqueue implementation is still not using the spool threadpool efficiently.
> We need RabbitMQ to use that threadpool to maximize concurrency in mail dequeuing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org