Benchmarks performance on HPC
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
CC @melonora @berombau
Working with Zarr files on a HPC may create problems due to Zarr v2. One of the challenges for the hackathon will be to setup a set of benchmarks, which will help evaluate the transition to Zarr v3.
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 locating the code paths that read and write Zarr v2 data and checking how Zarr v3 transition work is currently handled. Define benchmark cases that expose HPC-related performance or compatibility problems, then run them on representative HPC storage. Done means a documented benchmark set can compare the two Zarr versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hpc, python
- Domain
- hpc, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100