argumentcomputer / argumentcomputer/Megaparsec.lean
Performance: Profile Megaparsec to see where the bottlenecks are leading to poor performance
Open
- Dominant language
- Lean
- Stars
- 37
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
# Why?
It was reported that Megaparsec OOMs on 15KLoC of Lisp.
# What?
- [ ] Reproduce the issue
- [ ] Profile with `perf`
- [ ] Iterate identifying the bottlenecks
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported out-of-memory failure on 15KLoC of Lisp, then profile the parser with perf. Iterate on the profile to identify the bottlenecks; done means the poor-performance cause is identified and the findings are recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100