Lansweeper WebGUI and host server are lagging / slow

[Obi-Wan]

Hello guys,

our Lansweeper is lagging every day between 12 and 13 o'clock. This is particularly noticeable if we want to search for assets or want to open the detail page of an asset. Also the Windows server on which Lansweeper runs can also only be used to a limited extent. The CPU utilization rate at this time is more than 70 percent.

We've disabled the scanning targets in the affected period, but it didn't help.

Only the restart of the Lansweeper Windows service helps.

In the Windows event log we can always find a lot of the following entries:

"Category: Microsoft.AspNetCore.Server.Kestrel
EventId: 22

As of "02/07/2025 11:02:38 +00:00", the heartbeat has been running for "00:00:05.4423274" which is longer than "00:00:01". This could be caused by thread pool starvation."

By the way, is it normal that the errorlog.txt file is containing all errors since the installation? Maybe it would be better, that there will be cut at midnight and proceeding with a new file. At the moment, our errorlog.txt is about 425 mb... .

Kind regards,

[Tim_N]

Hello @Obi-Wan 

As you work with DavidPK on your support case, I wanted to provide a few things for you and future readers to look into and consider. 

Scheduling
In each of your scan targes, make sure your schedules for each aren't all running at the exact same time. I can see in your post that you disabled scans, but it's still a good idea to ensure scans are staggered to help spread the load. 

For reference, a /24 will take about 15 minutes for a complete "thorough" scan. This time will be shorter based on "Scanned Item Intervals". 

Scanned Item Intervals
You can modify the scanned item intervals to help speed up scanning as well. But, use this feature wisely. Modifying each item to be scanned too far apart could also mean inaccurate asset details. 

Threads
You can modify your IP and Computer threads (Configuration > Server Options -- scroll to the bottom of the page). This can be configured for a combined thread count of 100.

Finally, if you have thread count that is too high, and the target schedules start at the same time, and your IP target ranges are really large, it may take Lansweeper a long time to sort through and scan all of your assets. 

Suggestions
Schedule your scan targets throughout the day. Maybe asset types that don't change frequently (servers, networking, virtual hosts, etc) can be scanned after hours. Save the IP Targets where staff bring in roaming devices to scan during office hours. 

I hope some of these ideas help troubleshoot what's going on. I'm confident DavidPK will be able to help out. Please keep us posted. 

[Obi-Wan]

Hello David,

2 weeks ago, I have written our problem via the sales webform as mentioned here, because we were not able to open a support case directly. 

Since that time we have heard nothing from the support. Maybe you could contact your colleagues?

[DavidPK]

Hi Obi-Wan,

This is a situation that we would suggest submitting a support request. This would allow us to do more thorough investigation with logs and screenshots

  Please open a ticket in our support portal.

Make sure to add screenshots and the GatherLogs output file so our SME's can start investigating the issue straight away. 

Using the GatherLogs tool.