[jira] [Commented] (JAMES-3191) Key registration is slow

["Benoit Tellier (Jira)" <se...@james.apache.org>]

    [ https://issues.apache.org/jira/browse/JAMES-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123521#comment-17123521 ] 

Benoit Tellier commented on JAMES-3191:
---------------------------------------

https://github.com/linagora/james-project/pull/3408 solved the performance issue du to a rabbitmq overuse due to an infinite processing loop.

https://github.com/linagora/james-project/pull/3390 contributed reactive registration to the event bus

> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org