You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/contributing.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -264,4 +264,13 @@ If an existing Zarr format version changes, or a new version of the Zarr format
264
264
## Release procedure
265
265
266
266
Open an issue on GitHub announcing the release using the release checklist template:
267
-
[https://github.com/zarr-developers/zarr-python/issues/new?template=release-checklist.md](https://github.com/zarr-developers/zarr-python/issues/new?template=release-checklist.md>). The release checklist includes all steps necessary for the release.
267
+
[https://github.com/zarr-developers/zarr-python/issues/new?template=release-checklist.md](https://github.com/zarr-developers/zarr-python/issues/new?template=release-checklist.md>). The release checklist includes all steps necessary for the release.
268
+
269
+
## Benchmarks
270
+
271
+
Zarr uses [pytest-benchmark](https://pytest-benchmark.readthedocs.io/en/latest/) for running
272
+
performance benchmarks as part of our test suite. The benchmarks can be are found in `tests/benchmarks`.
273
+
By default pytest is configured to run these benchmarks as plain tests (i.e., no benchmarking). To run
274
+
a benchmark with timing measurements, use the `--benchmark-enable` when invoking `pytest`.
275
+
276
+
The benchmarks are run as part of the continuous integration suite through [codspeed](https://codspeed.io/zarr-developers/zarr-python).
0 commit comments