> Hmmm... My guess is that the problem is due to the load sharing + the > fact that multiple users access the Maildir at once, were it only 1 > server accessing the Maildir for all 20 users, it could eventually cache > the whole Maildir, or at the very least, you'd get a lot more cache > hits. But as two servers are accessing the share, neither can rely on > cacheing any of the data and must constantly go back to read it again. > 10 of the users are on one server and 10 are on another, neither server > can even > temporarily count on it's cache. Maybe those 20 users could all use > only 1 of the two systems so that that system is the only one accessing > the Maildir and won't have to constantly verify its cache is still > good... Just a shot in the dark.
Agreed. Not to mention, though, that I've seen pretty terrible performance of Maildir over NFS and wouldn't recommend it if it can be avoided. What's the network path from the NetApp to the mail server? What about its utilization? I'm assuming kernel nfs here and not userspace? And check out courier-imap's IMAP_USELOCKS variable, perhaps that's causing a slow-down. John -- John Madden UNIX Systems Engineer Ivy Tech State College [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id040&op=click -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id)95 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
