Max scan amount

[sullivane]

Is there any kind of "rule of thumb" for the max number of computers to scan at once?

Obviously, if my server\network can handle 50, I don't want to set it to 10 and vice versa.

Any complex mathematical equations that give a good idea?

[sullivane]

Thank you.

[Michael_V · Accepted solution]

If you are using SQL server: The default SQL connection pooling is set to 100 : https://msdn.microsoft.com/en-us/library/8xx3tyca%28v=vs.110%29.aspx

We open/close connections when needed, but don't change the windows/deployment threads too high or you will reach 100 SQL connections.

[sullivane]

Yeah, I know that it depends on server\network. I was wondering if anyone (or Lansweeper) has numbers or anything to try and get it close.

I have set it to 40\40\20, and I have been watching my resource monitor and everything seems ok so far.

I guess I will just watch it.

[sukaitsu]

It depends on your server and your network infrastructure. I use the following on each server.

Computer Threads: 36
IP Threads: 60
Deployment Threads: 32