defeated about Murder.....

[phr2101 at columbia.edu]

You have lmtpproxyd set up to query the murder master server for
each message that comes in.

You're options are to
1. Have lmtpproxyd query the local server for each incoming message.
This decreases load on the murder master. You do this by creating a
config file for lmtpproxyd and setting murder master to the
localhost. Then you just need to get the auth setup.

2. By pass the frontends, and have postfix deliver directly to the
backends

We did 1 for awhile, but would still have occasional (but a lot
fewer) problems (this is ~ 40K/hr of messages). We then switched to
2 (but using sendmail). We have the user/backend information in our
id system and just create a sendmail alias file for this.  This has
worked for months without problems.

-Patrick

Quoting Andrzej Kwiatkowski <andrzej.kwiatkowski at gmail.com>:

> Hi..
>
> I'was thinking that Murder is a very good concept for cyrus...
> Till today.
>
> I've started some performance test:
>
> I've 4 MTA with Postfix+Cyrus frontend 2.2.12
> 4 backend with Cyrus 2.3.6
> and 1 Mupdate with cyrus 2.2.12.
>
> I've started with smtp-stone sending
> 3000 msg (1000 for each of 3 users on 1 backend).
>
> Backend load was very low.
>
> But in this time mupdate have load about 1,5 (why ?)
> The concept was that mupdate is only for changing location of
> mailboxes... My frontend have information on mailboxes (checked
> with
> ctl_mboxlist -d) but they still are looking in mupdate which
> causes high load
> and SIGSEGV...
> Which causes lmtpproxy to drop connecitons and growing queue in
> postfix...
>
> Am i doing something wrong ?
> Authentication is doing by sasl digest-md5 to avoid SQL database
> performance,
> so i think this is no problem..
>
> So why mupdate causes such problems ?
>
> Thanks
> AK
> ----
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info:
> http://asg.web.cmu.edu/cyrus/mailing-list.html
>