We have run into an issue where the action of polling some counters creates CPU load on servers which is then returned in the CPU polling results. This can be considered artificial since the returned value is based on Orion's own polling, not processes normally running on the server. This can be avoided by adding a delay to CPU polling counters so that other components can finish up their WMI or RPC calls before the CPU counter is polled. This delay should be user configurable in the component monitor settings for WMI or RPC counters. Suggested default in the Windows 2003-2008 template is 3 seconds for the CPU PerfMon counter. All others should default to 0.
Support ticket related to this idea is: 370160
