nvim-orgmode / nvim-orgmode/orgmode
Performance tracking
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.9k
- Forks
- 190
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
Does this feature exist in Emacs orgmode core?
N/A
Orgmode link
No response
Feature value
The idea of this is to see which change introduced how much performance cost. Ideally, we can already see that something is hitting performance before it gets merged into master. Also, it's nice for performance-oriented refactoring.
I was thinking of a github action that will run a series of performance benchmarks on each commit (or PR?). Ideally, the result will be displayed in the UI. If that's not possible, one can look it up as a log in the github runner.
The master branch gets special treatment. Each benchmark is appended to a master performance-list we have stored somewhere™. Fancy graphs incoming.
Not sure how volatile the performance of github runners is though, that might be an issue.
Additional context
No response
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
No files, tests, or benchmark entry points are identified. Start by locating any existing performance benchmarks and CI workflows, then determine how benchmark results could be recorded for commits and pull requests. Done means a documented, repeatable workflow compares results and preserves a performance history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, lua
- Domain
- ci-cd, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100