> Been using 1.3.9 and now 1.4.1.1 (now running the .16) on Windows (win2k3) > and had no such an issue, the only real problem I faced was related to > the freshclam installed as a service and taking up too much CPU cycles, but > replacing it with a new version fixed the issue, other than that, I had > no CPU issue with ASSP; sure, the latest ".16" fixed a memory leak issue so now > the memory usage dropped, but, again, aside from that I had NO CPU issues
.16 seems better to me too. 9 hours and still low cpu avg. But I prefer to wait at least a full day before saying it's ok. What I don't get now is WHY the latest 1.3.x also caused me problems duuring the last 4 days. I had a old version running for weeks without any issue. Right now 1.4.x has about 20% more cpu avg than 'good 1.3.9x' and half the use of latest 1.3.9x I downloaded last Thursday. But that's an extimate, because I just upgraded to .16 there are also other differences, because 1.4.1x reports a larger number of messages processed per day (avg). But, again, I just got back from a short holiday and new .16 is running for less than 10 hrs tomorrow morning I'll verify perl.exe ram usage and will have better data about .16 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
