TCP I am writing a plugin for an application called DSpace. This opens a socket connection to the clam daemon and then sends the INSTREAM command. (As well I am using the IDSESSION and END commands.)
As a test, I opened a socket and INSTREAMed 1000 inputstreams for scanning. It runs fairly efficiently. As a second test, I scanned 1000 inputstreams, but opened and closed the connection each time. At first, I thought this was fairly efficent. Then the system started chugging away so that the sets of results each time I ran the tests did not make sense to me. ..\Wendy ..\Wendy Wendy Bossons Senior Software Engineer MIT Libraries Software Analysis and Development 77 Masachusetts Avenue Cambridge, MA 02139-4307 617-253-0770 wboss...@mit.edu<mailto:wboss...@mit.edu> On Nov 4, 2010, at 10:24 AM, Matus UHLAR - fantomas wrote: On 04.11.10 10:09, Wendy J Bossons wrote: What is the overhead of opening and closing socket connections to clamd? UNIX or TCP? I am trying to get some metric on that, but they are not making sense to me. What should be the amount of time in milliseconds that this takes, scanning x length files, different types of files, etc? Any information related to this topic would be helpful. Why are you interested? -- Matus UHLAR - fantomas, uh...@fantomas.sk<mailto:uh...@fantomas.sk> ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Boost your system's speed by 500% - DEL C:\WINDOWS\*.* _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
