leanprover-community / leanprover-community/mathlib4
Spikes in compilation + maximum resident set size
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 4.2k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Twice now, I've run into situations where the maximum resident set size has spiked due to increased compilation of one declaration.
#6998 and #6499 with Zulip threads
https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/Debugging.20procedure
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 by reviewing issues #6998 and #6499, then read the linked Zulip threads on the debugging procedure and the Seminorm.InstMulAction shortcut. Reproduce or characterize the compilation and maximum-resident-set-size spikes described there; the issue is done when the source of the increased compilation is identified and an agreed fix or mitigation is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100