hyj1991/v8-profiler-next

The idle usage statistics may be incorrect

LvPeng990324 opened this issue · 0 comments

Versions

  • nodeJS: v14.18.x
  • v8-profiler-next: v1.9.0

Problem 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.

img_v3_025m_a57acb63-fd8f-4bf9-8acc-df739b78dc9g