How to find out cause of very high '(program)' time in Chrome DevTools Performance profiler? #25796
-
|
When debugging Deno programs via Chrome DevTools I always see a high percentage of '(program)':
The hierarchical 'self' times don't add up, so I have no way of knowing what's eating up so much processing time:
Is this just a "me" thing? If not, I'm wondering how others debug performance bottlenecks with data like this? My understanding is that '(program)' means V8-internal, or Rust-internal. Are there perhaps debug flags I can add which would give DevTools more info? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
This is actually an upstream issue - see #21620 for the exact same problem. Indeed |
Beta Was this translation helpful? Give feedback.
-
|
Ah, thanks! |
Beta Was this translation helpful? Give feedback.
This is actually an upstream issue - see #21620 for the exact same problem. Indeed
(program)here means that we're in native code - usually it's some async code waiting to complete (eg. reading or writing from a socket), the "sync" rust code can be seen by looking forop_entries.