Print

Print


While I use IMAP, I personally haven't noticed too much of a slowdown.  
But I was having lunch with someone today and they commented on this. I  
would say it is becoming a big problem. They also mentioned that  
messages are being delivered out of order. For instance, Rich's reply  
showed up timely, but the original message wasn't received until hours  
later.

If you look at the NetApp cpu graph, it is 100% for much of the day:
        http://project.mail.msu.edu/cgi-bin/grapher.cgi? 
target=%2Ffiler%2Fnfs0;view=cpu

Probably the situation will improve in a few weeks when the students  
move away. But I hope the Mail team and the Provost ($$$) is on top of  
this problem for fall semester. (should we consider un-supporting IMAP  
as a backup plan? everyone move to Gmail?)

-John

CC'ed to NCC mailing list

On Apr 11, 2005, at 3:46 PM, Richard Wiggins wrote:

> Chris,
>  
> I checked with the Mail team and here's the scoop:  IMAP is  
> I/O-intensive (and especially read-intensive).  It imposes a lot of  
> load on the storage subsystem, which happens to be from a vendor  
> called Netapp.  At certain peak load times, the Netapp runs at full  
> throttle.  Through the APPR process ACNS requested funding this cycle  
> for new hardware to provide relief.  If the funding comes through they  
> should be able to address this concern this summer.
>  
> How often do you experience one minute transaction times?  What times  
> of day?   I don't do a a lot of IMAP, but when I do, performance  
> varies, but I don't think I've seen delays that long.
>   
> /rich
>  
> On Apr 11, 2005 3:25 PM, Chris Wolf <[log in to unmask]> wrote:
> Is anyone else noticing slowdowns with the mail.msu.edu servers,  
> especially for IMAP?  We aren't hearing complaints from our POP users,  
> but at least two of us using IMAP have been experiencing unusual  
> delays in ordinary mail operations for the last month or more, and  
> they've gotten even worse today.  Just trying to do something simple  
> such as opening a message to read it, deleting a message, or replying  
> to a message creates a delay of anywhere from ten seconds up to a  
> minute or more.  These operations used to take no more than two or  
> three seconds.
>
> --Chris
> ==============================================
> Chris Wolf                    Computer Service Manager
> Agricultural Economics        [log in to unmask]
> Michigan State University     517 353-5017
>