Skip to content

feat: Parametrize benchmarks for Zarr v2 and v3 formats (fixes #3757)#3818

Closed
abishop1990 wants to merge 1 commit intozarr-developers:mainfrom
abishop1990:issue-3757-parametrized
Closed

feat: Parametrize benchmarks for Zarr v2 and v3 formats (fixes #3757)#3818
abishop1990 wants to merge 1 commit intozarr-developers:mainfrom
abishop1990:issue-3757-parametrized

Conversation

@abishop1990
Copy link
Contributor

Refactored benchmarks to parametrize over zarr_format instead of separate v2 test suite.

Per maintainer feedback: 'better to reuse existing tests with parametrization'

Changes:

  • Extends existing test_read_array and test_write_array with zarr_format parameter
  • Tests both v2 and v3 formats with same benchmark infrastructure
  • Skips v2 + sharding combinations (unsupported in v2)
  • Single test suite covers both versions

All 5300+ tests passing locally.

- Extends existing read/write benchmarks to test both v2 and v3
- Parametrizes on zarr_format, compression, layout, and store type
- Skips v2 + sharding combinations (not supported in v2)
- Reuses existing test structure per maintainer feedback
- Provides performance comparison across Zarr versions

Addresses feedback: 'better to reuse existing tests with parametrization'
@d-v-b
Copy link
Contributor

d-v-b commented Mar 21, 2026

we should also add v2 / v3 parametrization to this benchmark:

def test_slice_indexing(

@abishop1990
Copy link
Contributor Author

Closing: Parametrized benchmark approach works locally but fails on py3.11-min_deps and macos py3.13. Issue #3757 remains open - maintainer feedback was good, but implementation needs debugging on CI matrix. Can reopen with better environmental understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants