datafusion-contrib / datafusion-contrib/liquid-cache
Flamegraph should report all threads not just one thread
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 452
- Forks
- 51
- Avg merge
- 3h 10m
- Merged PRs (30d)
- 12
Description
Currently I believe the flamegraph only report the stack trace of one thread, which is ok, but not great. We want aggregated flamegraph
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the flamegraph generation entry point and tracing where the stack trace for a single thread is selected. Determine how thread stacks are represented and how the flamegraph is produced; done means the output aggregates stacks from all threads rather than reporting only one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100