Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Interface baseline calculation frequency implications on system performance

Interface baseline calculation frequency implications on system performance

Table of contents

Performance Constraints

Performance issues and concerns are centered around the initial population of the statistical data, regular updates of the data during polling, and recalculations after any sort of database maintenance (data deletion and summarization).

This could have impact on the storage of historical data to the history tables.  If performance is an issue with continual updates, then a method of running updates only on a interval basis (like part of database maintenance) should be adopted.

Data storage should be minimal as there will be one entry per net object, per statistic, per time frame. For example, 1000 nodes, CPU Load, 2 time frames = 2000 rows.

Is the statistical data accurate?  Is my data "normal"?  – These questions are difficult to answer as each environment will differ per net object, so we can provide a "normality" test for the data given the available number of records, the valid range of data for the given value and the current standard deviation (
The normality test will consistently calculate if the data points follow the 68-95-99.7 rule and notify NPM how many times in the given data set a point would have triggered, a 3 standard deviation, and 4 standard deviation alert or threshold.

Last modified