Peter Marshall
Results
3
comments of
Peter Marshall
Yes it's expected that `CpuProfiler::StartProfiling` takes a few hundred ms, we've seen that before for big sites e.g. facebook.com. I am pretty sure the slow part is where we iterate...
Here is a repro just in V8 tests BTW: https://chromium-review.googlesource.com/c/v8/v8/+/2366695 Profiler startup takes ~4.8 seconds with 500k functions on the heap
Is the expected result that it shows up in node/lib/timers.js where this is implemented?