I installed uw-imap 2007e over the weekend, replacing 2006c. Things
seemed to be mostly working. Our server is Solaris 10. Users mostly
use Thunderbird (Mac & Windows) imap. A fair number of Apple Mail
users. A smattering of other clients.
BUT.... Today when the system got under load, our load average shot up
to about 100. All the processes at the top of top were imapd. We
couldn't tell what changed about imapd that was specifically the cause.
We had some reports of problems being worse on Windows TB than Mac TB
for at least one user that tried both. In general most of the users
seeing the worst of it were Windows users, but that may be just an
effect of the time of day (more Windows users in the morning).
We dropped back to 2006c and things seem better. The load is somewhat
high currently, but that's probably because of 4 hours of impaired mail
reading and users are catching up.
I just looked through the release notes
http://www.washington.edu/imap/documentation/RELNOTES.html
Not suprisingly, the notes don't mention (directly) that anything was
done that would impair performance. The only significant changes
mentioned are
2006i (COPYUID/APPENDUID)
2006k (mbx lock issue)
Is this performance hit a known issue? If so, any guidance on what we
might have seen? (I'm trying to move to MIX format, but the advice on
this list was to upgrade to the latest uw-imap version before seriously
using it.)
_______________________________________________
Imap-uw mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
