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

["Matthieu Baechler (Jira)" <se...@james.apache.org>]

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

Matthieu Baechler commented on JAMES-3191:
------------------------------------------

Did you run a profiler or use glowroot APM to have some insights on where the time is spent exactly ?

I have serious doubt that raising channel number from 3 to 10 will change latency from several minutes to some milliseconds

> 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