Lukasz Szybalski writes:
How can I figure out what the issue is with the imapd process? What it looks like after looking at it for last 2 months is minimal io usage, higher cpu usage for top 4 processes for about 4 seconds, before they get replaced by other 4 processes running at cpu for couple seconds. cpu for these ranges 32% to 94%. No other jobs. Lower network bandwidth ~20kb/s. Everything looks like we should be going at full speed.
Look in /proc to find the processes' current directories. Use strace to see what the processes are doing.
The likely scenario is a single user that has accumulated a huge folder. The server's default configuration just happens to allow a maximum of four sessions from the same IP address. You kill the user's process, the IMAP client immediately is able to log back in and start searching the same directory containing tens of thousands of files.
The IMAP server process is really a lightweight layer between the IMAP protocol and the filesystem. In order to support huge folders with hundreds of thousands of messages, the underlying filesystem will need to be able to deal with it.
pgp_Px7aUiXNX.pgp
Description: PGP signature
------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape
_______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
