Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENH: Merging results from sharded benchmarks #1362

Open
jackie-pc opened this issue Jan 12, 2024 · 0 comments
Open

ENH: Merging results from sharded benchmarks #1362

jackie-pc opened this issue Jan 12, 2024 · 0 comments
Labels
enhancement Triaged as an enhancement request

Comments

@jackie-pc
Copy link

Great work team - asv looks nice.

We are looking into using ASV for tracking benchmarks for the reflex project.

Some of the planned benchmarks can take a long time to run (say minutes), and we would ideally want to shard them out. E.g. one job runs suite A, another job runs suite B, another job run suite C, etc.

Would this be a sensible or supported workflow for asv? In particular I'm looking at the results/ dir. How would one merge results/ dirs produced by different jobs? With a valid merge operation, I can fan-in all the results in a single "publish" job at the end. This gives me a single static site to browse.

I am looking at results/benchmark.json in particular.... Each run seems to produce one of these. Is it as simple as just concatenating the list within all the benchmark.json's? :)

@HaoZeke HaoZeke added the enhancement Triaged as an enhancement request label Jan 27, 2024
@HaoZeke HaoZeke changed the title Merging results from sharded benchmarks ENH: Merging results from sharded benchmarks Jan 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Triaged as an enhancement request
Projects
None yet
Development

No branches or pull requests

2 participants