Skip to content

fix: handle NaN fill_value in array metadata equality (#3999)

CodSpeed / CodSpeed Performance Analysis failed May 25, 2026 in 0s

Performance Regression: -15.04%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 3 improved benchmarks
❌ 8 regressed benchmarks
✅ 55 untouched benchmarks
⏩ 6 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ WallTime test_slice_indexing[(50, 50, 50)-(slice(None, 10, None), slice(None, 10, None), slice(None, 10, None))-memory] 1.8 ms 2.1 ms -11.38%
⚡ WallTime test_slice_indexing[(50, 50, 50)-(slice(None, 10, None), slice(None, 10, None), slice(None, 10, None))-memory_get_latency] 4.1 ms 3.3 ms +27.08%
⚡ WallTime test_slice_indexing[(50, 50, 50)-(slice(10, -10, 4), slice(10, -10, 4), slice(10, -10, 4))-memory_get_latency] 237.2 ms 206.1 ms +15.07%
❌ WallTime test_slice_indexing[(50, 50, 50)-(0, 0, 0)-memory] 1.8 ms 2 ms -12.16%
⚡ WallTime test_slice_indexing[(50, 50, 50)-(0, 0, 0)-memory_get_latency] 4.1 ms 3.2 ms +26.44%
❌ WallTime test_sharded_morton_single_chunk[(32, 32, 32)-memory] 2 ms 2.3 ms -13.82%
❌ WallTime test_sharded_morton_single_chunk[(30, 30, 30)-memory] 1.9 ms 2.2 ms -13.56%
❌ WallTime test_sharded_morton_single_chunk[(33, 33, 33)-memory] 2 ms 2.3 ms -12.75%
❌ WallTime test_sharded_morton_write_single_chunk[(32, 32, 32)-memory] 195.9 ms 348.6 ms -43.79%
❌ WallTime test_sharded_morton_write_single_chunk[(30, 30, 30)-memory] 164.3 ms 292.6 ms -43.84%
❌ WallTime test_sharded_morton_write_single_chunk[(33, 33, 33)-memory] 218.1 ms 386.8 ms -43.62%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing main (c0e2afa) with main (51033fb)

Open in CodSpeed

Footnotes

  1. 6 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩