Replies: 4 comments 6 replies
-
If you know of a less resource-intensive alternative, you are welcome to share it. I do not see anything particularly demanding or unusual in this shell out to PowerShell in non-interactive mode. We obtain information about a single process and not all processes, to then filter them down to just one. I do not have any hypothesis as to what may be so CPU extensive. Perhaps your machine has really limited CPU resources, such as a single core. |
Beta Was this translation helpful? Give feedback.
-
What issue and where did you post it? In previous RabbitMQ versions, you would get a warning log message that If you'd like to fix this issue, please ensure Sysinternal's |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Sorry. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
Hello,
i have similar issue that i have posted some time ago but now regards the new logic present in rabbit 3.11.17 (erlang 25.3.2.1) on windows when is performed a check on the handle count, the command executed is the following:
c:/windows/system32/windowspowershell/v1.0/powershell.exe -NoLogo -NonInteractive -NoProfile -InputFormat Text -OutputFormat Text -Command "Get-Process -Id 3516 | Select-Object -ExpandProperty HandleCount"
This command is performed closely and on some machine can occupy a handful of seconds and the cpu is very high during this moments. This happen with windows 2019 server and powershell version 5.1.17763.3770 but not happen on windows 2022 and powershell version 5.1.20348.643 (with this s.o. the powershell execution is normal).
I have also attached an image with the cpu behavior on both system.
Thanks in advance for the reply.
Reproduction steps
Expected behavior
There is a solution in order to mitigate this problem with powershell ?
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions