This meta bug is to collect the "class" of performance issues involving large folders or high message volume  as backend activity (not manual message moves and the like) and that significantly impacts UI response or startup time. Source of performance hit is not limited to specific protocol or component. The goal is to give them focused attention and organization. Non-goal: we're not going to cover every possible performance bug here. If you are a user with a problem that involves very large folders or high message volume, and don't see your problem described in one of the bugs blocking this then please do not comment here, but please file a new bug and make it block this bug. This set is just the first pass.  Definition of very large folders or high message volume - I don't have a great defintion ready, it somewhat like, "I'll know it when I see it". I'll update the user story eventually. For now let's say an approximation is" * large folder - probably focused mainly on message count, say 5,000+ messages. But maybe also by message size, say >1GB * high message volume - one or more folders gets more than 50 messages on startup or in a short interval during the day
(mozilla-central bug 872497 was fixed 2013-05-19, TB24) I certainly don't expect these issues to be limited to enterprises, but I expect they will disproporrtionately affect enterprises, so blocking bug 564148
You need to log in before you can comment on or make changes to this bug.