Skip to content

chore(deps): upgrade nix to v0.32 - #203

Open
xtqqczze wants to merge 1 commit into
CodSpeedHQ:mainfrom
xtqqczze:deps-nix
Open

xtqqczze wants to merge 1 commit into
CodSpeedHQ:mainfrom
xtqqczze:deps-nix

Conversation

@xtqqczze

Copy link
Copy Markdown
Contributor

No description provided.

@greptile-apps

greptile-apps Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The dependency update appears safe to merge; no actionable regression was found.

Summary

Updates codspeed to use nix 0.32.0.

  • CodSpeed uses nix 0.32.0 for Linux timestamps.

Reviews (1) · Last reviewed commit: "chore(deps): upgrade nix to v0.32" · Reviewed by Greptile

@codspeed

codspeed Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Merging this PR will degrade performance by 8.09%

4 warnings, 1 note

⚠️ Unable to measure the execution of 59 benchmarks

These benchmarks measured no execution time, so their results are not comparable and count as unchanged. This usually happens when the compiler removes the code under test.

Prevent compiler optimizations

See affected benchmarks

⚠️ 17 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

⚠️ 6 benchmarks with a significant change ran on different hardware

Their base and head results were measured on machines with a different CPU, core count or memory, so the changes might not come from the code. Run base and head on the same runner type.

Learn more about Macro Runners

See affected benchmarks

⚠️ 7 benchmarks with a significant change ran in a different software environment

Their base and head results were measured with a different OS or toolchain, such as compiler, runtime or library versions, so the changes might come from this difference rather than from the code. Open an affected benchmark to see what changed.

See affected benchmarks

ℹ️ 39 benchmarks have no flamegraph

The flamegraph wasn't generated: no execution data was recorded while the benchmark ran. Make sure the compiler didn't optimize the benchmark out.

See affected benchmarks

⚡ 7 improved benchmarks
❌ 17 regressed benchmarks
✅ 594 untouched benchmarks

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ CPU Simulation spawn_on_parent_runtime 36.2 µs 60.3 µs -40.07%
❌ Walltime iter_batched_ref_large_input 5 ns 8 ns -37.5%
❌ CPU Simulation div 118.9 ns 174.4 ns -31.85%
❌ CPU Simulation iterative[5] 234.1 ns 289.6 ns -19.18%
❌ CPU Simulation iterative[10] 245.4 ns 300.9 ns -18.46%
❌ CPU Simulation iterative[20] 267.9 ns 323.5 ns -17.17%
❌ Walltime rem 5 ns 6 ns -16.67%
❌ CPU Simulation iterative[30] 290.4 ns 346 ns -16.06%
❌ Walltime add_two_integers[(65535, -65535)] 75 ns 89 ns -15.73%
❌ Walltime iter_batched_large_input 8 ns 9 ns -11.11%
❌ Walltime graph_coloring[6] 1.2 µs 1.3 µs -10.71%
❌ Walltime permutations[6] 68.8 µs 73.6 µs -6.56%
❌ Walltime spawn_on_parent_runtime 24.5 µs 26 µs -5.82%
❌ Walltime add_two_integers[(255, 255)] 19 ns 20 ns -5%
❌ Walltime add_two_integers[(42, 13)] 19 ns 20 ns -5%
❌ Walltime from_elem_decimal[1024] 201 ns 211 ns -4.74%
❌ CPU Simulation string_copy_with_bytes_counter 1.3 µs 1.4 µs -3.87%
⚡ Walltime hamiltonian_cycle[4] 1,295 ns 803 ns +61.27%
⚡ Walltime bench_array1[10] 6 ns 5 ns +20%
⚡ Walltime recursive_memoized[HashMap<u64, u64>, 10] 2.1 µs 1.8 µs +13.25%
... ... ... ... ... ...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

Tip

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


Comparing xtqqczze:deps-nix (d210722) with main (aa1bc87)

Open in CodSpeed

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.

1 participant