Re: SquirrelMail slow, VERY slow

["nathan r. hruby" <nhruby uga edu>]

On Wed, 25 May 2005, Doug Stewart wrote:

> Mark Dadgar wrote:
> > On May 25, 2005, at 11:24 AM, Doug Stewart wrote:
> >
> > > I've been tasked with setting up a SquirrelMail IMAP install for  our 
> > > intranet.  My users have been seeing *extremely* lengthy login  times, 
> > > sometimes on the order of 45 seconds - 1.5 minutes.  (The  webserver 
> > > running SM and the IMAP server are two separate boxes).
> >
> >
> > I see this using the out-of-the-box IMAP server when DNS resolution  is 
> > broken (my ISP manages to muck this up occasionally).
> >
> > Check that first.
>
> The two boxes know each other and can reach each other with no problems.  The 
> errors we're seeing (as far as the "INBOX" one goes) seem to be limited to a 
> few select users.

Yes, but that doesn't answer the question: Is your DNS horked?  Do you
have DNS?  Do lookups (forward and reverse) from both boxes for the other
box always return the same info?

> The general slowness affects everyone.  Those with smaller inboxes seem to be 
> *slightly* less affected, but not by much.

What IMAP server are you using on the backend?  This makes a big
difference.  I bet that these users with slow logins have really big
INBOXes and the IMAP server does not support the THREADED command that
SquirrelMail uses by default which is causing things to be slow (Eg: the
IMAP server needs to scan the whole mailbox to build the list of requested
headers and then MW has to thread them).  IIRC, this can be changed in
SM's config.

Additionally, you may be seeing a perf. hit if using mbox with mailboxes
larger than 200MB's on less than robust disks.

-n

--
-------------------------------------------
nathan hruby <nhruby uga edu>
uga enterprise information technology services
production systems support
metaphysically wrinkle-free
-------------------------------------------