Scan slowness

[brunotrevisan]

Hello everyone, I hope you are well.

I have 2 Scan servers, considering an environment that has an approximate number of 30k assets. We reduced the log retention period, but the environment is very slow in updating information and/or registering new assets, I'm talking about a period longer than 10 days to be able to complete the scan across the entire environment.
What could it be?
Another behavior that I believe is not normal is in the scan queue, it has accumulated hosts, where it quadruples the number of scans on certain assets. Even though I reset the queue it shows this type of behavior again.

[Tim_N]

Hello @brunotrevisan 

You have asked a very good question. There are many factors that can play into speeding up your scan targets. First, to set the playing field a little: I assume you are using On-Prem that is syncing with Lansweeper's cloud environment (we call it Lansweeper Sites). 

Let's talk about a few different areas: 

Scheduling
If you have parts of your network segmented out in vLANs for networking equipment, printers, switches, wireless, etc. you may want to consider scanning "non-moving" devices to scan at night only. Then, schedule your servers and workstations/laptops to scan during the day. That will ensure your assets that get turned off do get rescanned when they are supposed to. 

Multiple Scanners
By default, Lansweeper will not load balance your scan servers. You can assign specific scan targets to specific scan servers. 

Also, scanning vLANs is ideal. If you have a /16 network with tens-of-thousands of IP's, it can take a very long time to scan. Breaking up the schedules as stated above is idea. 

Multiple Scan Targets
By default, Lansweeper will create an AD and IP scan target. Therefore, your assets could be scanned via AD, IP, an agent, and SCCM in a single day. Consider reviewing your scan targets, schedule them to not overlap.

Scanning Threads
By default, the number of scanning threads is not maximized. Be cautious when making changes to threads as they can really overwhelm your server. Navigate to "Configuration > Server Options" and scroll to the bottom. There are "IP Threads" and "Computer Threads". IP represents Linux, switches, FW's, etc. Computer represents Windows. 

Making changes to threads will require a restart of the Lansweeper services. 

You can bump up the levels to a combined count of 99 total threads. When you bump them up, do it in small increments.... 5 to 10 at a time. After restarting the Lansweeper services, watch the performance of your servers while a scan is running. 

Bumping CPU and RAM isn't enough to increase performance. Make changes to the threads and compute together for greatest results. 

Scan Server Count
For 30k assets, you may want to deploy another scan server for a total of 10k per scan server. Typically, we like to suggest 4k to 7k assets per scan server BUT a single scan server can handle more if CPU, RAM, and IP threads are configured "properly" (each environment is slightly different). 

If we estimate 15k assets per scan server, you will need to have your threads boosted up pretty high--the exact configuration will depend on the majority of types of assets on your network. Make sure that the same scan targets are not duplicated in each scan server (unless required). Though not recommended, 15K assets per scan server is possible, but will require a "hefty" server configuration. 

These are a few ideas that came to mind when reading your post. 

Make some of these changes (or confirm the configuration) in your environment and let us know how this works for you.