-
|
I have a windows host connected with pulse-agent. the cpu is constant at ~20%. Is this normal for this high usage? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
The host agent should use very little CPU itself (<1%). If you're seeing 20% in Pulse, that's likely your Windows host's actual CPU utilization being reported, not the agent's own resource consumption. To verify: open Task Manager and check if Regarding monitoring cadence: the $env:PULSE_INTERVAL = "60s"
irm http://<pulse-ip>:7655/install-host-agent.ps1 | iexIf the agent process itself is consuming 20% CPU, that would be unexpected - let us know and we can investigate further. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the screenshots. That confirms what I expected - the pulse-host-agent is using 0% CPU (as shown in Task Manager), and the ~19% you see in Pulse is your Windows system's actual CPU utilization being reported. This is correct behavior. The agent just reads the CPU usage from the OS and reports it to Pulse - it's not causing the 19% itself. If you want to reduce how often the agent reports metrics (and slightly reduce network overhead), you can use the --interval flag as mentioned earlier. But the CPU reading itself is accurate. |
Beta Was this translation helpful? Give feedback.


Thanks for the screenshots. That confirms what I expected - the pulse-host-agent is using 0% CPU (as shown in Task Manager), and the ~19% you see in Pulse is your Windows system's actual CPU utilization being reported.
This is correct behavior. The agent just reads the CPU usage from the OS and reports it to Pulse - it's not causing the 19% itself.
If you want to reduce how often the agent reports metrics (and slightly reduce network overhead), you can use the --interval flag as mentioned earlier. But the CPU reading itself is accurate.