cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
d_i_saunders
Engaged Sweeper III
Hi,

We have 2 servers, scanning roughly 50% each of our pc's and addresses.

We have c.6000 pc and 600,000 IP addresses.

what is the best number of IP & Computer Threads to have configured, as I understand that SQL server has a max number of connections.. What I want to do is scan as much as possible as quickly as possible.

Server1:

IP Threads: 10
Computer Threads: 50

Server2:

IP Threads: 10
Computer Threads: 50

Anything I can do to improve this? More servers? or do we still have the SQL issue?

Thanks


6 REPLIES 6
Hemoco
Lansweeper Alumni
Yes, you can.
d_i_saunders
Engaged Sweeper III
so we can have 50 +20 on server 1 and 50+20 on server 2..?
Hemoco
Lansweeper Alumni
SQL has an internal connection pool limit of 100 (per remote machine). If you go higher, you will receive database timeouts.
Hemoco
Lansweeper Alumni
Your computer threads should be 50 at most and your IP threads 20 at most. We would recommend either narrowing down your IP ranges or setting up additional scanning servers, as it would take a single scanning server days to go through 300,000 IPs.
d_i_saunders
Engaged Sweeper III
Lansweeper wrote:
Your computer threads should be 50 at most and your IP threads 20 at most. We would recommend either narrowing down your IP ranges or setting up additional scanning servers, as it would take a single scanning server days to go through 300,000 IPs.


Thanks...

If I added another server are these still not limited by the total number of SQL connections?

d_i_saunders
Engaged Sweeper III
Anyone? No SQL expertabout?