John wrote:


Erik A. Espinoza wrote:

Another box shows about 28000 for VSZ, compared to 156556 here. Any
suggestions on why it's taking so much memory? Any suggested solutions?



Does one have a higher load due to more e-mail being processed than the other?
Do the machines have a different OS?
Do they have a different architecture?
Do they have different SpamAssassin plugins?
Are they the same version of SpamAssassin?

All of these are reasons why one machine would show different memory
usage on SpamAssassin....

Erik


Machine A: high mem usage. Machine B: not.
Same loads on both. Roughly same architecture (similar CPU's, same RAM).
Machine A runs kernel 2.6.9-42.0.10.EL, SA version 3.1.8 (with Rules du
Jour), QTP, Perl 5.8.5.
Machine B runs 2.6.9-42.0.3.EL, SA 3.1.7 (no Rules du Jour), no QTP, Perl 5.8.6. Removing all .cf's on Machine A then restarting qmail still displays 149552 VSize for each spamd process. Why so humoungous? With 512MB of RAM, I can't afford 156MB spamd processes. Any pointers appreciated (downgrade to SA 3.1.7?)

John



Today I uninstalled just the spamassassin-toaster, then reinstalled it. Spamd memory usage then showed very low. Next, I ran qtp-newmodel, which says spamassassin-toaster is not installed, so I let it install it. After all is done and qmail restarts (no Rules du Jour), memory usage shoots through the roof again--156MB spamd process and 2 children exactly the same. SA-toaster version 3.1.7. In the future perhaps I should avoid using qtp-newmodel...? In the meantime, I'd like to reinstall spamassassin-toaster as before. Can somebody tell me what other toaster packages I'll have to reinstall, and in what order (do not want to reinstall all of qmailtoaster)?

Thanks in advance,
John B.


---------------------------------------------------------------------
    QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to