I am not using on-access scanning.
when I type man clamd, I don’t get any information on threads.

I’ve tested setting MaxThreads to 100 vs 16(the amount of vcpus the scanner has), and I did not see a performance increase. 
What is the recommend setting for MaxThreads/MaxQueue for a 16 core system?

Also another question- Is there anyway to force clamd to use more RAM to increase performance. 

On Thu, Mar 4, 2021 at 10:55 AM G.W. Haywood via clamav-users <clamav-users@lists.clamav.net> wrote:
Hi there,

On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:

> ...  This is just one example of the many times the clamd process
> seems to pause or hang. ...

That looks to me like clamd is working as designed.  It has a queueing
system which manages threads doing different kinds of work.  If you
are giving the daemon a lot of work to do, under some circumstances it
will defer processing for some threads, based on a queuing algorithm.

For more information see the 'man' page for clamd (look for 'threads',
which should lead you to configuration options to experiment with) and
perhaps also .../clamd/thrmgr.c in the ClamAV source.

Are you using any on-access scanning?

--

73,
Ged.

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml