From: Jonathan A. <jo...@sq...> - 2003-04-02 19:06:22
|
Hello Lee, On Wednesday, April 02, 2003, Lee Brink wrote... > [If this is the wrong forum for this, please let me know] > I'm running SquirrelMail in production for a mid-sized University > (30,000+ students, staff, & faculty, <number> of simultaneous > connections) and I'm trying to get a sense of the hardware > requirements. What we're currently seeing is that SquirrelMail via > Apache chews up available memory very quickly (95% within two hours > or so), and then creeps towards 100% until it consumes all memory > and swap space. CPU utilization stays low (5-30% used) and the load > rarely cracks 1 during the entire time. On average we're seeing > 60-80 simultaneous connections at any given time. Something you may want to check is see if your IMAP server supports server side sorting. If it does, enable it in your config/config.php file... That often helps a lot. The other thing that often needs looking into is the IMAP server itself. Sometimes if an IMAP server is slow, apache/php/squirrelmail can chunk up a lot of memory processing the details. I've noticed this in particular with UW-IMAP because of the method of storing mail results in a long time to process large mailboxes. Also the default compile of UW-IMAP stores mail in ~/ which results in all files being read in that directory, even those that aren't mail folders. -- Jonathan Angliss (jo...@sq...) |