Greetings -
I've now got as far as playing with the imaptest10 test utility to
see if I can stress-test our development server. imaptest10 is built
against dovecot-1.0rc28
It may just be that I'm excessively heavy handed, but when I let
imaptest10 rip with the command...
./imaptest10 user=test%03d host=testserver.imap.york.ac.uk clients=50
mbox=./dovecot.mbox msgs=1000 secs=30 logout=10
...after 15 seconds or so I started getting output along the lines of:
Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo
100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 10%
30% 5%
2 0 1 1 1 0 0 0 0 0 0 50/ 50
2 0 0 1 1 0 0 0 0 0 0 50/ 50
0 0 2 2 0 1 1 1 1 1 0 50/ 50
2 0 2 2 0 1 1 1 1 1 2 50/ 50
0 0 1 1 0 0 0 0 0 0 0 50/ 50
- 16. stalled for 16 secs in LOGIN
- 17. stalled for 16 secs in LOGIN
- 18. stalled for 16 secs in LOGIN
2 1 1 2 1 0 0 0 0 0 0 50/ 50
- 17. stalled for 17 secs in LOGIN
- 18. stalled for 17 secs in LOGIN
- 22. stalled for 16 secs in LOGIN
- 23. stalled for 16 secs in LOGIN
- 24. stalled for 16 secs in LOGIN
1 0 1 1 0 0 0 0 0 0 0 50/ 50
- 17. stalled for 18 secs in LOGIN
- 18. stalled for 18 secs in LOGIN
- 22. stalled for 17 secs in LOGIN
- 23. stalled for 17 secs in LOGIN
- 24. stalled for 17 secs in LOGIN
- 28. stalled for 16 secs in LOGIN
- 29. stalled for 16 secs in LOGIN
- 30. stalled for 16 secs in LOGIN
- 31. stalled for 16 secs in LOGIN
- 32. stalled for 16 secs in LOGIN
The "stalled" log lines continue until the test completes. I'm
assuming it's just that I'm pushing our hardware beyond its
reasonable limits: it is only an oldish development box...
Sun v120 with 1 650MHz SPARC processor and 1Gbyte RAM
Dovecot is using shadow password file authentication. The mail
folders are in Maildirs, NFS-mounted from a NetApp filer, and each
account's INBOX has around 1000 messages in it. Control and Index
files are on local disk.
By the end of the 30 second test run load average has climbed to
around 11
I don't know how "active" the imaptest10 utility is when it's
running, but do you think I should be concerned by the "stalled"
messages? That is, do you think I have something configured amiss?
Or is it likely just to be I'm expecting too much of our hardware?
(The real system will have beefier Suns with Opteron-based CPUs, more
memory, etc)
With thanks,
Mike B-)
PS. I forgot to say: despite all this activity there's not a single
error logged by Dovecot in the (admittedly short at this stage) test
runs.
--
The Computing Service, University of York, Heslington, York Yo10 5DD, UK
Tel:+44-1904-433811 FAX:+44-1904-433740
* Unsolicited commercial e-mail is NOT welcome at this e-mail address. *
On Wed, 2007-03-28 at 18:07 +0100, Mike Brudenell wrote:> ...after 15 seconds or so I started getting output along the lines of:..> Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo > 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 10% > 30% 5% > 2 0 1 1 1 0 0 0 0 0 0 50/ 50 > 2 0 0 1 1 0 0 0 0 0 0 50/ 50It's logging in pretty slowly..> - 16. stalled for 16 secs in LOGINTry changing http://wiki.dovecot.org/LoginProcess settings, especially login_process_per_connection=no and see how much it helps. Also you could use logout=0 parameter to imaptest to avoid the login/logout overhead. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070328/c4d8ae43/attachment.bin>
On 28 Mar 2007, at 18:15, Timo Sirainen wrote:>> - 16. stalled for 16 secs in LOGIN > > Try changing http://wiki.dovecot.org/LoginProcess settings, especially > login_process_per_connection=no and see how much it helps.Sorry I forgot to give my current login and auth settings (which, I have to admit, I thought I'd tuned to be reasonable/generous for the eventual environment)... login_process_size = 64 login_process_per_connection = no login_processes_count = 10 #login_max_processes_count = 128 #login_max_connections = 256 #auth_process_size = 256 auth_cache_size = 1024 auth_cache_ttl = 600 #auth_worker_max_count = 30 auth default { passdb shadow { # [blocking=yes] - See userdb passwd for explanation #args } userdb passwd { # [blocking=yes] - By default the lookups are done in the main dovecot-auth # process. This setting causes the lookups to be done in auth worker # proceses. Useful with remote NSS lookups that may block. # NOTE: Be sure to use this setting with nss_ldap or users might get # logged in as each others! #args } }> Also you could use logout=0 parameter to imaptest to avoid the > login/logout overhead.Re-running the test with logout=0 didn't help :-( ... % ./imaptest10 user=test%03d host=testserver.imap.york.ac.uk clients=50 mbox=./dovecot.mbox msgs=1000 secs=30 logout=0 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% 5 1 1 5 1 0 0 0 0 0 25/ 25 [50%] 3 2 0 2 0 0 0 0 0 0 34/ 34 [68%] 3 1 2 3 0 0 0 0 0 0 43/ 43 [86%] 1 1 1 2 0 0 0 0 0 0 46/ 46 [92%] 2 1 1 3 0 1 1 1 1 1 50/ 50 1 0 0 0 0 0 0 0 0 0 50/ 50 2 2 1 3 0 0 0 0 0 0 50/ 50 2 1 1 1 1 0 0 0 0 0 50/ 50 0 1 0 1 0 0 0 0 0 0 50/ 50 1 1 1 1 0 1 0 1 1 1 50/ 50 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% 2 0 1 3 1 0 0 0 0 0 50/ 50 1 0 0 1 0 0 0 0 0 0 50/ 50 1 1 1 1 0 0 0 0 0 0 50/ 50 1 0 0 0 0 0 0 0 0 0 50/ 50 1 1 2 2 0 1 0 1 1 1 50/ 50 - 12. stalled for 16 secs in LOGIN - 13. stalled for 16 secs in LOGIN - 15. stalled for 16 secs in LOGIN 1 0 1 2 0 0 0 0 0 0 50/ 50 - 12. stalled for 17 secs in LOGIN - 13. stalled for 17 secs in LOGIN - 15. stalled for 17 secs in LOGIN - 17. stalled for 16 secs in LOGIN - 19. stalled for 16 secs in LOGIN - 20. stalled for 16 secs in LOGIN - 21. stalled for 16 secs in LOGIN - 24. stalled for 16 secs in LOGIN ... -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *