Separating master processes for different services to utilise multiple cores/cpus
Raymond T. Sundland
raymond at sundland.com
Wed Feb 25 18:09:27 EST 2009
When master receives a connection, it spawns a child process to manage
that connection. That would essentially make it multi-threaded making
use of the multiple CPUs when needed, I would think. Is that not the
case? You can launch multiple master processes, but that wouldn't have
any better guarantee to use multiple CPUs, either.
Atif Ghaffar wrote:
> Hello,
>
> I am a long time cyrus user but have not been hands on for a while.
> At my current job we are running cyrus to manage all mailstore for our
> ISP.
>
> Recently I have migrate a couple of boxes to newer ones with more
> cores per cpu.
>
> when running htop -u cyrus, i see that only one core is being used
> for most of the work and that seems to be a waste of the rest of the cpus.
>
> We are using the following services (imap, pop3, lmtp, sieve)
>
> One thought that comes to mind is to run different master processes
> which do one service at a time.
>
> I am thinking on consolidating into
>
> 1. cyrus-master-main (running imap/sieve)
> 2. cyrus-master-pop3 (running pop3)
> 3. cyrus-master-lmtp (running lmtp)
>
> Does this makes any sense?
> Would this balance the usage of the CPUs.
>
> If yes, I will post the config files for inspection.
>
>
> best regards
> Atif
> ------------------------------------------------------------------------
>
> ----
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20090225/bc82c6fa/attachment.html
More information about the Info-cyrus
mailing list