My apologies for taking so long to respond to this posting (From
06/16/2003) on this list. I'm the one who wrote the original posting.
Here's an update of the situation.
Our SquirrelMail installation still is having massive performance
problems. There's a memory leak that requires a web server restart every
few days, and response times will tank (2+ minutes or more) regardless of
load or memory usage. To date no one has been able to pinpoint the
problem.
Here's a recap of our setup:
Sun E420 (IIRC) with 2 CPUs, 4G RAM, and 16G disk space running Solaris 8
Apache 1.3.27
PHP 4.2.3 with the following configure directives:
--prefix=/server/sw/33 --with-apxs=/server/sw/prod_apache/bin/apxs
--enable-force-cgi-redirect --with-gettext --with-iconv --with-ldap
--with-java=/server/sw/prod_java --enable-mbstring
Sun's J2SDK v1.4.1.02
OpenLDAP v2.1.19
SquirrelMail v1.2.11 with the following plugins: quota-usage v1.0,
retrieveuserinfo v0.8, filters (With spam filtering turned off)
SquirrelMail has been modified to support:
- on-the-fly determination of a user's IMAP server (There are 8 IMAP
servers and the user's setting is stored in a user configurable LDAP
field).
- authentication methods to verify a user against our Kerberos master
between the web server & the user.
- authentication between the web server and the IMAP servers using
Kerberos (We refer to it a Kerberos Proxy Authentication)
There are so many pieces to this puzzle it has been an exercise in
frustration (And massive head banging) in trying to discover the
performance problems and fix them.
Our plan to discover what's causing the memory leaks is to set up a
dedicated IMAP and web server, strip SquirrelMail down to it's minimum,
and build all the software with the absolute minimum needed to support
SquirrelMail. Then we plan to use automated load tools to simulate user
load, and add all the pieces we need to support our users one at a time &
see where the greatest slowdowns are. It's going to take a long time, but
I think it's the best way to discover the imapct each piece has on
performance.
In the mean time I've hacked v1.4.1 of SquirrelMail with all our local
mods. It's going into production to replace our current version of
SquirrelMail at the end of the month. Hopefully we'll see an improvement,
but I don't expect a solution to all our performance problems from this
upgrade.
For a user base of 8,000 currently, with the plan to have a total user
base of 30,000 potential users in the middle of August (Current estimates
put actual usage at 60-75% of that) we're not doing nearly as well as we
should, but not as bad as we could be.
I'll post anything I find as we go through our testing to this list.
Lee
PS: If anyone wants to me to talk about my experience getting
SquirrelMail out to the entire Cornell community or the hacks I've done to
SquirrelMail to support our environment let me know. I don't have a
problem talking about any of it in great detail, but I don't want to bore
people with it if no one's interested. And if anyone else is running
SquirrelMail with a large user base like me, speak up! I want to hear
about your experience.
--
When people pushing a political agenda tell you that you should be willing
to "make sacrifices for your country," cover your wallet. When they quote
John F. Kennedy to support their case, run away. And when they lie about
what Kennedy said, run away screaming. - Donald L. Luskin, 5/22/03
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
--
squirrelmail-users mailing list
List Address: [EMAIL PROTECTED]
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
