This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Community FAQ
Register | Log In
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Lansweeper Community
- Forums
- General Discussions
- Max scan amount
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Register to ask a question, start a topic or share an idea
Join the Community
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 04:04 PM
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?
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?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 08:18 PM
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.
We open/close connections when needed, but don't change the windows/deployment threads too high or you will reach 100 SQL connections.
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 08:25 PM
Thank you.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 08:18 PM
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.
We open/close connections when needed, but don't change the windows/deployment threads too high or you will reach 100 SQL connections.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 07:58 PM
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.
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 06:59 PM
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
Computer Threads: 36
IP Threads: 60
Deployment Threads: 32
Thank you,
Jeffrey Smith
Enterprise Applications Security
(319) 499-6310
JefSmith@geico.com
General Discussions
Find answers to technical questions about Lansweeper.
New to Lansweeper?
Try Lansweeper For Free
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now