[
https://issues.apache.org/jira/browse/JAMES-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17115814#comment-17115814
]
Gautier DI FOLCO commented on JAMES-3191:
-----------------------------------------
I have a few questions:
# How did you discovered it was related to the channel number?
# Why do we need RabbitMQ for a SELECT?
Maybe it is not the channel problem, but the lock time, in this case, we might
do more than just sending a message over RabbitMQ, and we should prepare the
message, then request the channel.
> Key registration is slow
> ------------------------
>
> Key: JAMES-3191
> URL: https://issues.apache.org/jira/browse/JAMES-3191
> Project: James Server
> Issue Type: Improvement
> Components: eventbus, IMAPServer
> Affects Versions: master
> Reporter: Benoit Tellier
> Priority: Major
> Labels: perf
>
> We noticed that on *master* SELECT IMAP command is significatively slow
> (several minutes) on top of the distributed profile. (See attached
> instrumentation average time and percentiles)
> A quick performance review links this to listener registration (by key).
> A code review leads to:
> - The low channel number (3) maybe this count can be safely raised to a
> higher number? Like 10? Maybe even configurable?
> - EventBus::Register operation is handling IO but is synchronous. The
> reactor scheduler backing it up is unspecifed (thus is likely the parrallel
> one). We should let the caller specify the scheduler he whishes to run.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
