Performance Shift(s): `efd356de`

[github-actions]

Benchmark comparison has identified performance shifts at

• commit efd356d ([pre-commit.ci] pre-commit autoupdate #5107).

Please review the report below and take corrective/congratulatory action as appropriate 🙂

Performance shift report

       before           after         ratio
     [bf33b029]       [efd356de]
     <main~1>         <main>    
+      4.08±0.2ms       4.90±0.5ms     1.20  experimental.ugrid.ConnectivityLazy.time_create(6)
+        9.21±1ms       12.0±0.9ms     1.30  experimental.ugrid.MeshCoordLazy.time_bounds(10000)
+        274±10ms         354±30ms     1.29  experimental.ugrid.MeshCoordLazy.time_bounds(1000000)
+      8.21±0.6ms       10.6±0.7ms     1.29  experimental.ugrid.MeshCoordLazy.time_bounds(6)
+      3.07±0.4ms       4.28±0.5ms     1.40  experimental.ugrid.MeshCoordLazy.time_points(10000)
+      6.45±0.6ms       8.25±0.5ms     1.28  experimental.ugrid.MeshCoordLazy.time_points(1000000)
+      3.04±0.4ms       4.26±0.4ms     1.40  experimental.ugrid.MeshCoordLazy.time_points(6)
+        21.9±3μs         30.0±3μs     1.37  experimental.ugrid.MeshLazy.time_add_coords(6)
+        21.3±3μs         27.5±2μs     1.29  experimental.ugrid.MeshLazy.time_connectivities(6)
+        25.7±4μs         32.4±3μs     1.26  experimental.ugrid.MeshLazy.time_coords(6)
+        114±10ms         159±10ms     1.40  experimental.ugrid.MeshLazy.time_eq(1000000)
+        41.0±3ms         55.4±6ms     1.35  experimental.ugrid.MeshLazy.time_eq(6)
+        22.9±3μs         30.5±3μs     1.33  experimental.ugrid.MeshLazy.time_remove_connectivities(6)
+        41.0±6μs         51.5±4μs     1.26  experimental.ugrid.MeshLazy.time_remove_coords(6)

Generated by GHA run 3690071488

[trexfeathers]

I wonder what happened, because it definitely wasn't due to the changes in the commit!