Skip to content

Make the zarr DataTree latency benchmark report changes - #11812

Merged
headtr1ck merged 2 commits into
pydata:mainfrom
headtr1ck:asv-zarr-latency-repeat
Oct 26, 2026
Merged

headtr1ck merged 2 commits into
pydata:mainfrom
headtr1ck:asv-zarr-latency-repeat

Conversation

@headtr1ck

@headtr1ck headtr1ck commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

Description

Follow-up to #11810: use repeat = 1 in IOReadDataTreeZarrLatency, so asv can report changes in it, and drop the 21 groups case.

  • With repeat = 3, every commit gets 6 samples (2 processes). For 6 vs 6 samples, asv's two-sided Mann-Whitney test can at best reach p ≈ 0.00216, above its p < 0.002 threshold, so no change is ever reported. In the benchmark run of #10742, the ~1.9x speedup was marked as not significant (~0.52) and left out of the comment.
  • With repeat = 1 (2 samples per commit), asv compares the 99% confidence intervals instead, which flags that speedup (checked with asv's compute_stats and is_different). It is also cheaper.
  • The 21 groups case shows the same ratio as 71 groups, so only 71 groups are benchmarked now.

AI Disclosure

  • This PR contains AI-generated content.
    • I have tested any AI-generated content in my PR.
    • I take responsibility for any AI-generated content in my PR.
      Tools: Claude Code

🤖 Generated with Claude Code

With repeat = 3 every commit gets 6 samples, for which asv's Mann-Whitney
test can never reach its p < 0.002 threshold, so the speedup of pydata#10742 was
not reported.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@headtr1ck headtr1ck changed the title Use repeat = 1 in the zarr DataTree latency benchmark Make the zarr DataTree latency benchmark report changes Oct 26, 2026
@headtr1ck
headtr1ck enabled auto-merge (squash) October 26, 2026 14:50
@headtr1ck
headtr1ck merged commit 4f0b616 into pydata:main Oct 26, 2026
50 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🥱 No significant changes. Boring, in the best possible way.

Comparing a43eed7e (this PR merged into the base branch) with 960d99a8 (base branch).
Only changes by more than a factor of 1.5 are shown, see the workflow run for all results.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant