Benchable should not uncompress builds for every iteration
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
run-snippet will then call run-smth:
https://github.com/perl6/whateverable/blob/9b747bc43e61f340295e1fc497f0535d460554d3/lib/Whateverable.pm6#L405-L407
run-smth is basically a wrapper that takes a block and wraps some logic around it to uncompress and then delete builds. So the for ^ITERATIONS logic should be inside that block, otherwise it will spend a lot of time just uncompressing stuff.
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 referenced loop in bin/Benchable.p6 and follow run-snippet into run-smth in lib/Whateverable.pm6. Check how builds are uncompressed and deleted around the benchmark block, then run the relevant Benchable flow to verify that a build is unpacked once for all iterations rather than once per iteration.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100