Am Montag, 13. August 2012, 13:32:31 schrieb Kevin A. McGrail: > My immediate thought is to lower the numbers of jobs for the > masscheck but I am overall unaware of the memory impact for > masscheck. > > Anyone have some feedback on the memory footprint for their masscheck?
I've formerly had 6 processes, now I'm at just one - still a huge memory needed. The SPAM folder I use has 6000 mails, 240MB. Not a lot in terms of memory, but the mass-check process grows to >5GB? This is the output of "ps axuw": spamuser 12989 43.3 81.8 4144816 3649524 pts/0 R+ 21:42 0:42 /usr/bin/perl -w ./mass-check --progress --cache --cachedir=/temp --all -n --mid ham:mbox:/tmp/masslearn_ham.2892.IHtp25eT.mbox spam:mbox:/tmp/masslearn_spam.2892.GvEoB13q.mbox You see that took "just" 3.6GB RAM, still way too much. What's my problem here? -- // Michael Monnerie, Ing.BSc. ---------------------------------- Sorcerers have their magic wands: powerful, potentially dangerous tools with a life of their own. Witches have their familiars: creatures disguised as household beasts that could, if they choose, wreak the witches' havoc. Mystics have their golems: beings built of wood and tin brought to life to do their masters' bidding. I have Linux. ----------------------------------
signature.asc
Description: This is a digitally signed message part.
