[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ZMailer under load
- To: zmailer@nic.funet.fi
- Subject: ZMailer under load
- From: "Dawid Kuroczko" <qnex42@gmail.com>
- Date: Mon, 4 Dec 2006 12:25:57 +0100
- DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=D/5Exjj/MWAUgJo+CM8JSMm9yz8gncuigUjcDoAovjpEw9nuJPX4Z58Qlf+FbnMWGdTaxkbZLVmqXQ6TQtJbm9j2JXmnzraEV2rTp48D4l1JX+XaFhgD9HV5pN054v+rvI+5m3OUSCQ2dTCwr+tsxNjeTM81M7PGW7FGhPB8ovk=
- Original-Recipient: rfc822;zmailer-log@nic.funet.fi
- Sender: zmailer-owner@nic.funet.fi
Hello,
I'm writing this mail to broaden my knowledge and learn some neat tricks.
I have a ZMailer cluster which generally works good but from time to time
we are hit by a severe load and sometimes system grinds to a halt with
queues over 800 000 mails and rising.
The reason was I guess I/O contention. The scheduler is competing
for I/O with a bunch of happy other processes and loses. I guess the
simplest soultion is 'get more drives' (and it works), but I would like to
know if I overlooked any other ways to help my system.
I'm looking for any kind of hints, like ways to tuning Linux, or perhaps
even switching to some other OS. All replies appreciated.
As a side note I was thinking about decoupling scheduler into two
separate entities, one doing scheduling (mostly non-blocking) and
the other doing queue scanning. Would that be a good idea?
Regards,
Dawid
-
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi