A year and a half ago we put two qmail-scanner machines in our lineup, handling around 100,000 messages per day. The second was mainly for redundancy. We're now netting on average 400,000 messages per day and our two machines are just barely hanging on for the ride. We've got new hardware on order to remedy our situation, but my question are: What kind of mileage are you seeing out of your servers? Does anyone have any tips for squeaking any more performance out of qmail-scanner/clamd?

Does anyone have any experience with:
- precompiling qmail-scanner - I've seen a little information about this, but nothing that doesn't have HUGE warnings about being experimental.
- Memory File System - I've done this before, but never with QS, would it be worth my file to do this for /var/spool/qmailscanner/working? In theory it sounds good, but is this something that's duplicating the caching the operating system is already doing? - clamd - Right now we're set up with very thorough scanning, is there any magic which can lighten the load on clamd.


We're using FreeBSD 5.3 on these servers, relatively average hard drives, and 2G of memory. The new servers will be P4 3.2's and the old ones are Duron 1200's.

Thank You,

Cody Baker
[EMAIL PROTECTED]
http://www.wilkshire.net



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Qmail-scanner-general mailing list
Qmail-scanner-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general

Reply via email to