[
https://issues.apache.org/jira/browse/JAMES-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3652.
---------------------------------
Resolution: Fixed
Merged
> Avoid locking in protocol task execution
> ----------------------------------------
>
> Key: JAMES-3652
> URL: https://issues.apache.org/jira/browse/JAMES-3652
> Project: James Server
> Issue Type: Improvement
> Components: IMAPServer, POP3Server, SMTPServer
> Affects Versions: 3.6.0
> Reporter: Benoit Tellier
> Priority: Major
> Labels: perf
> Fix For: 3.7.0
>
> Attachments: with-lock.png, without-lock.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I found out the JMX executor wrapper of the Netty protocol transport layer
> was doing locks (synchronized lists and synchronized blocks).
> On a regular SMTP worload (5000 mails of 500 KB) we spent 12.9% of CPU cycles
> doing locks... (See attached flame graphs)
> We can easily implement the very same feature without any lock. Wich result
> in using 4.7 % only of CPU cycles.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
