How should profiling interact with worker-threads? about pprof-nodejs

[nolanmar511]

Thanks -- I hadn't yet experimented with worker_threads.

Long term, I assume the goal for pprof-nodejs will be to have profiles which are collected outside of worker threads include information about worker threads, so I'm not extremely concerned that profiles cannot be collected within worker threads (except that it does make me think there will be some complications for collecting profiles which include information about worker threads).

Experimenting a bit here, though, the profiles collected right now when there's a worker thread are rather strange.

Heap Allocations, for example, seem to be attributed to call stacks somewhat randomly. The first time I profiled, heap allocations from within the worker were attributed to "keys"; the next time, they were attributed to "Lines":
heap-1.pb.gz
heap-2.pb.gz

The wall profile was more within expected behavior. It was 100% idle, since it only profiled the main thread.
wall.pb.gz

The script I used is attached:
index.js.txt

[nolanmar511]

At this point in time, I don't think this is a feature request that can be prioritized for pprof-nodejs.

Marking as closed (I think a fix here would likely require upstream changes)

[dmitryuk]

Same issue