On 4/27/12 3:46 AM, G.W. Haywood wrote:
It does seem odd to me that people appear to be running ClamAV on
memeory constrained systems. I'd suggest that those systems might not
be suitable for the task.
Adding memory to an older Sparc system does not affect the signature loading
time at all. It only determines how many third-party signatures you can finally
load. An 8G system is the same as a 2G system in this regard. Adding a second
processor doesn't change anything, either. I've built and run it on far faster
Sparc systems and they never keep up with an equivalent Intel system even when
using all the available optimizations in the compiler.
As for why, one of these servers has been running non-stop since 2001,
interrupted only by patching and a colo outage. One 500mHz proc, 2G ram, 72G
mirrored storage in a cheap 1U package and it more than keeps up with the
workload. It is a mail list server that also handles 90 vanity domains.
$ uptime
7:43am up 748 day(s), 22:43, 0 users, load average: 0.47, 0.39, 0.39
Speaking of Oracle systems, I'm running ClamAV on several Oracle Database
Appliances with Oracle's Linux and the load times are measured in seconds for
the core signatures. Will be adding it to some Exadata and ZFS storage appliance
systems shortly and I expect it will be fairly painless to load and scan the
user space. So yeah, throwing hardware at a problem can both solve and mask
problems.
dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
