You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my project, the CPU usage is often close to 100% recently. I want to use the v8-profiler-nex to help me locate the problem. But when I installed it in production environment to capture data on resources occupied by methods, during another time period when the CPU occupied 100%, the captured data actually showed that most of the CPU occupied was the (idle) function. I think this result is incorrect, but I am not sure. I would like to ask about this situation.
I can't figure out why (idle) takes up so much cpu.
The text was updated successfully, but these errors were encountered:
Versions
nodeJS
: v14.18.xv8-profiler-next
: v1.9.0Problem Description
In my project, the CPU usage is often close to 100% recently. I want to use the v8-profiler-nex to help me locate the problem. But when I installed it in production environment to capture data on resources occupied by methods, during another time period when the CPU occupied 100%, the captured data actually showed that most of the CPU occupied was the
(idle)
function. I think this result is incorrect, but I am not sure. I would like to ask about this situation.I can't figure out why
(idle)
takes up so much cpu.The text was updated successfully, but these errors were encountered: