We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If an add-on uses too much CPU, it should be stopped for security reasons.
Research: https://nodejs.org/api/process.html#process_process_cpuusage_previousvalue https://gist.github.com/pmuellr/8c349726392bb47da680410eb7904092 https://stackoverflow.com/questions/7773826/how-to-find-out-the-cpu-usage-for-node-js-process#answer-44657880
The text was updated successfully, but these errors were encountered:
I believe a side effect of doing this would be breaking ARM support: #23
Sorry, something went wrong.
No branches or pull requests
If an add-on uses too much CPU, it should be stopped for security reasons.
Research:
https://nodejs.org/api/process.html#process_process_cpuusage_previousvalue
https://gist.github.com/pmuellr/8c349726392bb47da680410eb7904092
https://stackoverflow.com/questions/7773826/how-to-find-out-the-cpu-usage-for-node-js-process#answer-44657880
The text was updated successfully, but these errors were encountered: