Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > High CPU usage spikes when monitoring multicast devices

High CPU usage spikes when monitoring multicast devices

Table of contents


In order to determine multicast routing, NPM must determine the status of all multicast devices in a defined group. These devices may be spread across multiple pollers, and group members may change regularly as devices use and stop using multicast channels. Polling operations and database Insert, Update, and Delete operations that are required to update the database may cause spikes in CPU usage on both your polling engines and your database server.


The best approach to resolve this issue is to spread the multicast polling load by staggering multicast polling times. This polling management is performed automatically in SolarWinds NPM version 10.6.

To correct the issue of high CPU usage on polling engines and database servers due to multicast polling, upgrade your SolarWinds NPM installation to version 10.6. For more information, see Network Performance Monitor or download the upgrade from the Customer Portal.

Last modified