[
https://issues.apache.org/jira/browse/JAMES-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rashid Mahmood updated JAMES-3086:
----------------------------------
Description:
After functional tests, we are performing load tests against James Server setup
with Casandra/Elasticsearch(cassandra-ldap-guice) packaging option. With JMeter
constant throughput timer of 300 SMPT requests per seconds we are achieving
around 10 requests per seconds. Each Request is with 100KB attachment. Observed
CPU of the machine (where MailServer running) was over exhausted.
Many of the threads in thread dump were in awaiting notifications state.
I see around 100 threads from Elastic search, is there any configuration to
control this?
Where is the bottleneck?
!image-2020-03-04-09-30-30-054.png!
See the thread dump in attachment.
was:
After functional tests, we are performing load tests against James Server setup
with Casandra/Elasticsearch packaging option. With JMeter constant throughput
timer of 300 SMPT requests per seconds we are achieving around 10 requests per
seconds. Each Request is with 100KB attachment. Observed CPU of the machine
(where MailServer running) was over exhausted.
Many of the threads in thread dump were in awaiting notifications state.
I see around 100 threads from Elastic search, is there any configuration to
control this?
Where is the bottleneck?
!image-2020-03-04-09-30-30-054.png!
See the thread dump in attachment.
> Mail Server Load Test giving very low throughput
> ------------------------------------------------
>
> Key: JAMES-3086
> URL: https://issues.apache.org/jira/browse/JAMES-3086
> Project: James Server
> Issue Type: Bug
> Components: POP3Server, SMTPServer
> Affects Versions: 3.3.0
> Reporter: Rashid Mahmood
> Priority: Blocker
> Attachments: image-2020-03-04-09-30-30-054.png, threaddump.txt
>
>
> After functional tests, we are performing load tests against James Server
> setup with Casandra/Elasticsearch(cassandra-ldap-guice) packaging option.
> With JMeter constant throughput timer of 300 SMPT requests per seconds we are
> achieving around 10 requests per seconds. Each Request is with 100KB
> attachment. Observed CPU of the machine (where MailServer running) was over
> exhausted.
> Many of the threads in thread dump were in awaiting notifications state.
> I see around 100 threads from Elastic search, is there any configuration to
> control this?
> Where is the bottleneck?
> !image-2020-03-04-09-30-30-054.png!
>
> See the thread dump in attachment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
