> > I have been under the apparently false presumption that spamd prcessed
> > its messages in memory (perhaps this explains why each spamd process can
> > oft take up to 25% cpu?).  I recently looked in /tmp and found lots of
> > left over spamassassin.xxxx.xxxxxx.tmp files (the first four x's are
> > numeric, the second set of x's are alpha-numeric).
> > 
> > I am interested in placing those files in a tmpfs, but do not want to
> > put my whole /tmp directory under tmpfs.... but I can't for the life of
> > me find any configuration settings that tell spamd where to place its
> > temp files.  Do I need to change something in the code itself?
> 
> nope -- setting the std env var TMPDIR  will do it.  those files are
> created if you're using Pyzor or DCC.

Thank you kindly!  

Might I ask if anyone else has gone with any type of ramdisk for this directory 
and if so
if it helped in any way (just five minutes running it so far; I don't see any 
significant
performance gain)?  I am wondering how to size it as well.  I have started out 
with a
64MB tmpfs, but not sure if I'll need more.  I am tempted to size it similar to 
the
following recommendation from a how-to for creating a ramdisk for amavis:

n * (1 + max(expansionfactor)) * $message_size_limit

Thoughts anyone?  What else could be eating up so much CPU??

> > Pointers to anything I missed or other help greatly appreciated!  I am
> > running 3.0rc5 (as I understand it, only documentation changes were made
> > between rc5 and the official release), Fedora core 2, 2.8GHtz
> > hyperthreaded Pentium IV, 1 GB RAM, spamc out of Courier Maildrop to
> > spamd.  Spamd pounds my system all day long (cpu but not memory).  I run
> > max-children beween 5 and 8 (and all user prefs in (My)SQL, as well as
> > AWL and Bayes, although I cannot run bayes/awl without mail backing up,
> > as it appears to be too slow).


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to