Mike Sanchez wrote: > I run clamd .80 on Solaris 2.7 and call File::Scan::ClamAV from perl to scan > messages.
Old Solaris version on an old Sparc with not much RAM? > With .80 top shows clamd < 5%, but on occasion once or twice a week climbs > to 20% - 30%. Really bogs down the system until clamd is restarted. 20 - 30% is not high load, you shouldn't need to restart clamd. What really "bogs down" the system is swapping due to the size of RAM. I have an old Sparc5 with 64 MB which only SpamAssasin and a high load of messages can bring down... I disabled SpamAssasin, just use MailScanner w/o it; and that old Sparc5 used to spend all day at 100% CPU when I was compiling and building stuff and it still delivered all mail. > I installed .84 on test system that already had .80, hoping CPU load issue > would not be seen in .84. CPU load with .84 is actually higher, with jumps > to 50%-60%. If you are not doing real benchmarking those numbers are meaningless. So it was 60% but under what real load (messages per second)? Is clamd doing the same work or perhaps the 60% was with some really nasty zip inside zip virus? If you only look occasionally at load (and BTW using top increases the load, you should be using prstat) you cannot reach any conclusion. > Anyone have any suggestions with .80 or .84 CPU load issue. Tune up clamd. That means adjusting the MaxConnectionQueueLength, MaxThreads, ArchiveMaxFileSize, ArchiveLimitMemoryUsage options on clamd.conf taking into consideration that RAM is limited. Tune up Solaris... you're not using XWindows right? Do some real benchmarking, otherwise there is nothing to evaluate results against, nothing to set objectives. I know this doesn't help much, but just throwing some numbers doesn't do it either. -- René Berber _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
