Peter P. Benac wrote:
Sorry for picking this thread up late, but I was curious if you have run any performance monitoring tools on this box or are you just assuming the SM is the culprit. At the very least have you run and monitored TOP on this machine to see who your top processes are.
I'm using top and also Spotlight, so that I can monitor pretty much everything at a glance. And it isn't just one machine--I tried it on two 280s and now it's on a 4-processor machine I borrowed. The 4-processor is handling the load, but fast logins--like every 2.5 seconds, can push the LA way up.
My mail server is on a E-220-R dual 450Mhz's and performance has never been
an issue with my mail clients.
How many users? Which IMAP?
Are you running NFS on this machine and is NFS hard or soft mounted? Is
there any processes on this machine using RPC's heavily.
No and no. Nothing but SM and what it needs (apache, mysql, php...) Does your LDAP
server use a DB backend or are you using flat files?
LDAP is on another machine; it's iPlanet. What process is being
used for authentication? Are the clients seeing a degradation is performance and what do they call "slow"? Do you have non-SM mail users on this system and what kind of performance are they seeing?
LDAP for auth, and yes, I saw performance problems when the public was using it. But the machines I'm testing on do nothing but SM.
Once a user is authenticated to the mail server LDAP should have very little to do with this. At that point is all between the Web Server, SM and the what ever IMAP Server you are using.
Right. And what I keep finding is that the LA and CPU usage (and only CPU) shoots up on every login. If logins are spaced out that isn't a problem, especially on the more powerful 4-CPU system.
So the load problem is caused by whatever SM does at login--the first mail pull? caching? sorting?
begin:vcard fn:Lesli St. Clair n:St. Clair;Lesli email;internet:[EMAIL PROTECTED] version:2.1 end:vcard
