System is slow - High Memory Consumption of IIS Worker process

[tuccero]

Hello,

We have a standalone on-prem installation of Lansweeper (both SQL server and IIS is installed on same machine) and recently we observed that the system is very slow.

The latest events that happened prior to the slowness was that we have added SCCM in the scanning targets and also we exceeded the assets limit according to our current license. Im not sure if that makes any difference or not.

Due to the fact that we are using lansweeper for many years i did a search to find out if the resource requirements of the VM are matching with the latest versions.

I found the article below which is pretty recent so i changed the memory to 16GB:

https://community.lansweeper.com/t5/general-discussions/scanning-server-requirements/td-p/13335

I also limited the maximum memory of SQL Server to 8GB in order to allow some memory for IIS and OS needs.

The slowness continue so yesterday i updated to the latest version (12.4.0.2) hoping that it would be a bug of the previous version.

Even after updating to latest version though the system is still slow.

I am sharing with you some screenshots indicating the system resources, processes consumption and the paging space as well because i noticed that the page size is too big.

So i am wondering whether i need to set a maximum limit also in IIS application pool, set strict values for paging or if the issue is something else.

Please advise

[tuccero]

Hello,

In addition to the above, note that the scanning server stopped scanning for around 1 month now.

The last successful scan for any asset was done in March

[DavidPK]

Hi,

In addition to the general system resources, it's also critical to review your Lansweeper scanning configuration:

• Scanning Schedules:
  • Are scans occurring too frequently? Overlapping scans can significantly increase resource consumption.
  • Consider staggering or reducing the frequency of scans, especially full scans.
• Scanning Item Intervals:
  • Lansweeper allows you to configure how often certain items are scanned. Some of these can be very resource-intensive:
    • Certificate Scanning: This can involve retrieving and analyzing certificates from many devices, which can be CPU-intensive.
    • Firewall Scanning: Scanning firewall rules can also consume resources, especially if there are many rules.
    • Driver Scanning: Enumerating all installed drivers can be a time-consuming process.

[tuccero]

Hello,

Thank you for the provided information.

I reviewed the scanning schedules and i did some changes to them as well as the scanning time intervals.

I will monitor the server in the next few days to see if that helps.

[tuccero]

Hello,

It seems that the utilization of the VM remains at the same level as before.

There is still very high memory utilization with IIS Worker Process consuming around 13GB from the total 16GB of the VM.