On Mon, Feb 8, 2010 at 8:59 AM, Freddie Cash <fjwcash@xxxxxxxxx> wrote: > On Mon, Feb 8, 2010 at 8:27 AM, Ken D'Ambrosio <ken@xxxxxxxx> wrote: >> >> Hey, all. For various reasons, I've been asked to have an account with >> slightly over a million e-mails divvied up between thousands of folders. >> Shockingly (that's a joke), SquirrelMail doesn't seem too happy with >> thousands of folders; after (roughly) 30 seconds, it times out, never >> showing me either the messages in the inbox, nor the side panel with >> folders. I've grepped for "timeout" in both the Squirrelmail sourcecode >> and php.ini, and don't see anything that seems appropriate that I haven't >> already tweaked. (Note that I'm assuming it's a timeout issue, but I >> suppose it could also be a memory consumption issue.) >> >> Since I don't need zippy response times, and I've got lots of memory, I'm >> more than willing to throw in otherwise-unreasonable values... but some >> pointers on what to tweak (and where) would be gratefully accepted. Did you search before asking? http://squirrelmail.org/wiki/SquirrelMailPerformance http://squirrelmail.org/docs/admin/admin-6.html > Which IMAP server is this connecting to? What format are the folders on the > server? And are there any local filters enabled in SM? > If the backend IMAP server is using mbox for mail storage, then you'll want > to turf it. There's not way this will work in any kind of safe, fast, or > reliable way. mbox is not suited to even hundreds of messages in a single > folder. > If the backend IMAP server does not use server-side sorting, server-side > threading, and server-side filtering, then you'll want to enable those > before accessing it via any IMAP client. If the IMAP server doesn't support > those, then turf if. There's no way this will work if you have to process > everything in the client. > Finally, disable local mail filters in SquirrelMail. And configure it to > use server-side threading and sorting. No, threading won't help performance. It should be disabled. > One you have a robust IMAP server that handles all the processing (sorting, > threading, filtering, etc) on the server, then SM will work fine. I have > several accounts with hundreds of folders, thousands of messages, > multiple-GB of used storage, and things are very snappy in SM 1.5.1. But > that's with Cyrus IMAP on the backend doing all the heavy lifting. Use of version 1.5.1 is strongly discouraged. It is many years old and contains numerous published security exploits. If you use 1.5.x, you should be using 1.5.2 (which has updated mailbox cache code that is slightly faster). -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
