5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Scaleability
FromSent OnAttachments
Hans du PlooyMar 15, 2005 8:36 am 
Ricky ChanMar 15, 2005 8:49 am 
Michelle KonzackMar 15, 2005 11:44 am 
Hans du PlooyMar 16, 2005 9:50 am 
Hans du PlooyMar 16, 2005 9:55 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] ScaleabilityActions...
From:Ricky Chan (rick@brightview.com)
Date:Mar 15, 2005 8:49:01 am
List:net.sourceforge.lists.courier-users

I have courier running as a backend for webmail app for more than 400,000 users without a problem. You will find imap is not the biggest problem, I found the slowest thing was the webmail application itself.

As it is webmail, you won't find a lot of imap sessions running (as you would with a normal imap session/client). It connects does what it needs to do and disconnects.

Because of this I run it across 6 machines with a load balancers in front of them using network attached stoeage for data store. (Courier hasn't caused me many issues over NFS unlike other (I won't name them) imap servers).

If you don't need it, I would turn off imap keywords, I notice some performance improvements. There is various notes in the distrubtion config file also about performance gains if you turn off some features (expecially if your webmail doesn't support it).

As I said, webmail is more likely to be a bottle neck then anything else (even with optimised setups) when compared with imap.

Ricky

Hans du Plooy wrote:

Hi guys,

I'm wondering, how scaleable is courier-imap? I have to implement an imap server (to backend a web mail) for 400,000 users. Can courier-imap handle this? Specifically the imap part, the rest I'm not worried about.

Thanks