Does profiler work with stack-switching instructions?
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 512
- Forks
- 51
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 21
Description
This may be just a question: Should I expect the profiler to work with suspend/resume, or is it completely not implemented? I'm running a program that takes about 3sec to run but the profiler gives 0.001778s as the top-line "nested" value. I don't know if that should be considered a bug or just unexplored territory.
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 reproducing the reported program and profiling its suspend/resume execution, since the issue names no files or tests. Determine whether the profiler is expected to account for stack-switching instructions and whether the reported 0.001778s value is incorrect; document the finding and identify the relevant profiler entry point or test if follow-up work is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100