memprof: group allocations on traces by trace number
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Tarantool
Since: 2.10
Root document: https://www.tarantool.io/en/doc/latest/book/app_server/luajit_memprof/
Dev issue: https://github.com/tarantool/tarantool/issues/5814
SME: @ igormunkin , @ Buristan
Details
We already know the number of a trace being executed where an allocation event happens. So we can simplify debugging by reporting not INTERNAL: but TRACE [n]: with the allocation event. It enables users to compare this output with jit.dump() and so on.
Contributor guide
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 with the memprof root document at tarantool.io/en/doc/latest/book/app_server/luajit_memprof/ and review the development issue at github.com/tarantool/tarantool/issues/5814. Trace how allocation events are currently reported and identify the relevant validation steps; done means events report TRACE [n] rather than INTERNAL and can be compared with jit.dump() output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100