This is an great piece of work Sudip, thanks, it helps me a lot. -----Original Message----- From: Sudip [mailto:[EMAIL PROTECTED] Sent: 16 October 2003 19:13 To: James Users List Subject: Re: Stress test on James
More details on the test scenario 1) OS: Used Red hat 9.0 2) We had a varying message size, but not exceeding 10K 3) 3 hops 4) Network between the servers: 100 MBit 5) The client sending the mails was stationed on another server Sudip ----- Original Message ----- From: "Serge Knystautas" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Thursday, October 16, 2003 12:58 PM Subject: Re: Stress test on James > Sudip, > > This is great!! Couple of questions: > - Operating system? > - What message size? Have you tested the impact of varrying message > size to see how that impacts? > - How many processor/repository hops were there within server1. For > instance, if the messages arrive in root, go to transport, then remote > delivery puts it in its own spool, I would call that 3 hops. > - Network between server1 and server2? 100 mbit? > - Where was the client(s) sending messages to server1? Was it on > server1, or on another machine(s)? > > But in general, this is just great news! We still want to work on > outgoing delivery speed, but 2600 messages/sec is really very pleasing. > I'm ready to drop MSSQL as my repository database and move to MySQL now! > > -- > Serge Knystautas > President > Lokitech >> software . strategy . design >> http://www.lokitech.com > p. 301.656.5501 > e. [EMAIL PROTECTED] > > Sudip Shekhawat wrote: > > Finally we have some real numbers!! The stress test on James concluded. > > > > Test Scenario: > > 1. We used two servers running james 2.2.08a. We start by sending ‘n’ > > mails/min to server1. Server1 processes these mails and sends them to > > server2. Server2 ghosts the mails. > > 2. The servers were 2.4 Ghz Pentium 4 with 1 GB of memory. > > 3. We used mySQL 4.0.13 and JDBC connector 3.0.9 > > 4. JDK 1.4.2 was used with the –server option and we also set the JVM > > heap to be 384 MB. > > 5. By using trial and error and some logic we came up with the > > optimal number of spool threads to be 12 and the outgoing threads to be > > 20 for server1. > > 6. Server2 used 100 spool threads. > > 7. Maxcache was set to be 125. > > 8. We used james database repository. By making james and james’s > > database repository use the same server leads to contention of CPU time > > and james doesn’t perform to its fullest. Therefore the database > > repository (mySQL) was installed on a different server. > > 9. Max connection for the database was set to 20. > > > > Method: > > 1. We started by sending 800 mails/min to server1. We were constantly > > following up with the spool size of James. > > 2. We kept increasing the mails/min till we saw a rate when james > > couldn’t handle 100% of the mails. > > > > Results: > > 1. James was able to process (receiver/process/send) all of the 800 > > mails/min. > > 2. As we increased the rate, James comfortably processed around 2600 > > mails/min with a CPU usage of 70% for James and the CPU usage of 30% for > > mySQL > > 3. When we reached 2800 mails/min, the spool started increasing in > > size and the number of mails processed per min started decreasing. The > > decrease was exponential with the increase in the number of > > messages/min. When we sent 4000 mails/min, james processed 400 mails/min. > > > > Conclusion: > > James with our current configuration can handle 2600 mails/min which is > > pretty neat. > > > > Thanks > > Sudip > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
