Hi,
Finally, I managed to run the same scenario as described below with
2.3.0a1. 80603 mails sent, 0 lost. Performance seems to be basically
identical which is good news.
I will continue with more mails per minute, larger attachments and
longer runs...
And I'm looking forward to try and reproduce Stefanos improvements in
big mail handling (20MB) soon after they have been commited.
Also, I'd like to encourage people to look at JAMES-442 and comment on
the test tool itself and the test which should be run. Personally, I'd
like to have memory footprint data recorded and
multithreading/scalability/errorhandling improved. But what's more?
Ralf Hauser suggested to base it on JMeter which sounds like a good idea
to me. Any thoughts on this from someone already familiar with the
JMeter codebase?
Bernd
Bernd Fondermann wrote:
Hi,
I conducted the first longer test run using the code from Jira JAMES-442.
The test ran without any problems under vanilla 2.2.0 for 24hrs, 80612
mails were sent, 0 lost.
It simulates the following scenario:
50 internal users.
100 external addresses.
| mail |
| proc.|
| per | | MIME part size|
| min |from| to | text | binary |
+------+----+----+------+--------+
| 20 |int |ext | 1000 | 1000 |
| 10 |ext |int | 500 | - |
| 1 |ext |int | 200 | 30000 |
| 20 |int |int | 500 | - |
| 1 |int |int | 100 | 30000 |
======
52
What numbers would make more realistic average usage scenarios? More
mails? More users?
There is a problem running the tool under 2.3.0a1, hopefully I can get
it working over the weekend for a first comparison of 2.2 and 2.3 branches.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
