Any way to improve the performance of ME for very large mailboxes?
It seems to really start to have issues for clients with 50GB+ mailboxes, especially when all of that is in 1 folder. We've recently imported some clients that have extremely large mailboxes and this has been an issue for them where they didn't have issues previously in the other system, so we've had to move them back into the old system.
Very large mailbox performance
-
- Posts: 48
- Joined: Mon Feb 22, 2021 8:30 pm
Re: Very large mailbox performance
We had problems with users that had 10gb inboxes.
Anytime MailEnable gets a big "folder", be it Inbox or a sub-folder, that account's performance, and then by extension, the server's performance degrades significantly.
The only resolution was to break up folders. We had to roll our own solution that would use MailEnable dlls to run the internal archive function and push large sums of messages off to Archive folders. This dropped the size of the inbox and broke the folder sizes down enough that ME could keep up. We had to roll our own that ran on the command line because the Webmail interface would timeout during archiving operations and would affect all of webmail until it was restarted. We found the speed issue had to do with xml files being used as index stores, which are absolutely horrible for performance when the xml is read, and re-written anytime a message is moved, added, deleted, whatever.
Anytime MailEnable gets a big "folder", be it Inbox or a sub-folder, that account's performance, and then by extension, the server's performance degrades significantly.
The only resolution was to break up folders. We had to roll our own solution that would use MailEnable dlls to run the internal archive function and push large sums of messages off to Archive folders. This dropped the size of the inbox and broke the folder sizes down enough that ME could keep up. We had to roll our own that ran on the command line because the Webmail interface would timeout during archiving operations and would affect all of webmail until it was restarted. We found the speed issue had to do with xml files being used as index stores, which are absolutely horrible for performance when the xml is read, and re-written anytime a message is moved, added, deleted, whatever.