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 2021/09/04 10:29:00 UTC
[jira] [Closed] (JAMES-1283) JamesMailSpooler should use different
threadpools for dequeue and processing
[ https://issues.apache.org/jira/browse/JAMES-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-1283.
---------------------------------
Resolution: Fixed
This is the behaviour of James 3.7.0-SNAPSHOT
> JamesMailSpooler should use different threadpools for dequeue and processing
> ----------------------------------------------------------------------------
>
> Key: JAMES-1283
> URL: https://issues.apache.org/jira/browse/JAMES-1283
> Project: James Server
> Issue Type: Task
> Components: SpoolManager & Processors
> Affects Versions: 3.0-M2
> Reporter: Norman Maurer
> Priority: Major
>
> At the moment we start X threads which concurrent consume mails from the MailQueue. So if you have for example have 100 threads and only one is needed you waste resources. We should better use X threads to dequeue and Y threads to process. So we could for example use 2 threads which dequeue and pass the mails to worker thread pool that does the mail processing. This should be more efficient
--
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