Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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