Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > SWIS on primary server uses too much RAM/CPU in Orion system with additional pollers

SWIS on primary server uses too much RAM/CPU in Orion system with additional pollers

Created by Robert Stidman, last modified by Karen Valdellon_ret on Jul 13, 2016

Views: 634 Votes: 0 Revisions: 2

Updated July 13, 2016

Overview

This article addresses the issue where SolarWinds Information Service uses up too much RAM (over 1.5 GB) and or CPU utilization (100%) on the main server after upgrading to NPM 12 and other products on the same Orion Core version in a system that utilizes additional pollers.

Environment

NPM v12 and related core products

Cause 

This occurs when some modules on some pollers have not been upgraded and cause excessive processing for the SolarWinds Information Service.

Resolution

Complete all upgrades on all pollers for all modules and verify that all pollers are running the same Orion modules.

 

 

 

Last modified

Tags

Classifications

Public