Idea: benchmark JITs against fast_blank
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 119
- Forks
- 36
- Avg merge
- 14h 21m
- Merged PRs (30d)
- 6
Description
We're likely not going to get the full perf but I wonder how much closer we get by enabling a JIT
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 the repository's existing benchmark setup and the linked fast_blank project. Investigate how to benchmark Ruby JITs against fast_blank, then compare the results and document how much performance is recovered when JIT is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100