Version: Unreleased Build from the github repo on 1/27/15
Operating System: Windows 2008 R2
Steps to Reproduce:
- Install a build of Topbeat that includes the process's command line in the output on a Windows system.
- Spawn a large number of processes on the host.
- Observe high CPU utilization in the WMI Provider Host (WmiPrvSE.exe) process.
This issue was discussed in the forums at https://discuss.elastic.co/t/windows-topbeat-causes-high-cpu-utilization-in-wmi-provider-host/42649.
The high CPU utilization is believed to be because Topbeat does not cache the commandline of processes so it must make a WMI query for every process on the system every time it collects data.
Version: Unreleased Build from the github repo on 1/27/15
Operating System: Windows 2008 R2
Steps to Reproduce:
This issue was discussed in the forums at https://discuss.elastic.co/t/windows-topbeat-causes-high-cpu-utilization-in-wmi-provider-host/42649.
The high CPU utilization is believed to be because Topbeat does not cache the commandline of processes so it must make a WMI query for every process on the system every time it collects data.