Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Collector Data Processor causes high CPU and memory utilization

Collector Data Processor causes high CPU and memory utilization

Updated June 16, 2017

Overview

This article describes an issue where the SolarWinds Collector Data Processor is running at 80% or more and the CPU usage is at 100%.

Environment

NPM 11.5 or earlier

Cause 

MSMQ is unable to write the result of the polling jobs to the database when the process runs out of memory. The MSMQ folder (C:\Windows\System32\msmq\Storage\) is not full when checked.

NPM 11.5 uses a 32-bit Collector Data Processor and is able to access up to 1 GB of memory per 1 processor.

Resolution

SolarWinds recommends upgrading to NPM 12.0 to fix the issue.

 

Last modified
18:41, 15 Jun 2017

Tags

Classifications

Public