Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"WMI Provider Host" progress occupy so mush cpu in windows platform #67

Closed
moriyalb opened this issue Jun 27, 2018 · 3 comments
Closed

Comments

@moriyalb
Copy link

when I use pidusage in node(10.1.0), i found that "WMI Provider Host" progress is cost so much cpu resources, and my computer is slowly sometimes I need to reboot it.

Do anyone know how to fix this?
the use of pidusage is in a setInterval callback each second.

@soyuka
Copy link
Owner

soyuka commented Jun 27, 2018

Do anyone know how to fix this?

I wish! we tried a lot of things to improve windows retrieval of cpu/memory usage (see issues #19 #32 ).

sometimes I need to reboot it.

You should be able to restart the service called "Windows Management Instrumentation service" instead from Services.msc.

Please do check the "Event Viewer" and the logs inside WMI-Activity maybe that there are some errors?

@moriyalb
Copy link
Author

Thank you. I don't really use it on Windows platform. now my code just like

if (os.platform == "windows")
setInterval(pid_checking, 100000)
else
setInterval(pid_checking, 10000)

and now it works well.

@soyuka
Copy link
Owner

soyuka commented Jul 24, 2018

Closing as wont fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants