> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Todd Lyons > Sent: dinsdag 8 maart 2005 0:23 > To: 'ClamAV users ML' > Subject: Re: [Clamav-users] ClamAV 0.83 - Stream scanning timeout > > > Mark wanted us to know: > > >Yesterday, I subjected ClamAV to a very rigorous, final > >stress test. I let it scan roughly 20,000 news spool files, > >and opened an individual connection for each file (not very > >efficient, of course, but good to get massive concurrency; > >especially since I ran 5 simultaneous instances of the test-script). > >Needless to say, ClamAV was quite busy. :) But passed the test > > What did you use to do this test? Homegrown scripts?
Yes. Nothing fancy, though; just a 'quick-and-dirty' Perl job. > Did you have a local news spool? Yes. Testing this over NFS, or something, would serve no purpose. > Can you offer up some info and possibly code? I'd > love such a beast for testing on our systems here. Well, I attached the test script. Like I said, I ran 5 concurrent instances of this script, just to see how ClamAV would handle threads (or whether it would buckle, even). This test was typical for my machine, where there may be a sudden spike in connections (from the news queue-runner, for instance, or SMTP). - Mark
clamavtest.pl
Description: Binary data
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
