Through an oversight in a server configuration file, about a week ago
a different partition was unintentionally mounted as the pop temp
directory on our main popper server.
In the past after reading all the available performance info, I had
deliberately set this server up so the POP temp directory would be the
same partition as the mail spool, to enable the "fast update"
optimizations when running in server mode. When a different partition
was mounted for that directory, I was expecting we would take a big
performance hit.
Instead the performance seems to have significantly increased on the
server, average load decreased, and the peak 5-minute load over the
past week has been 1/3 of what it was the week before. I don't
understand why this should be; it seems like there should be equal or
higher disk I/O load on the mail spool partition because the user mail
file has to be both copied off and copied back whenever there are
updates to it relating to a POP session.
Now I'm thinking of leaving it this way. Anybody have an idea why it
should have worked this way?
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED]
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
