Update Elixir and Rust deps - #58
Merged
Merged
Conversation
Refresh mix.lock (benchee 1.5.1, dialyxir 1.4.8, ex_doc 0.40.4, jiffy 2.0.2, stream_data 1.4.0) and move glazer from ~> 0.5 to ~> 1.0: 0.5.15 is retired on hex. glazer 1.0 keeps the API the benchmarks use (compile_path/1, find/2, validate_utf8, force_utf8) and UTF-8 validation stays opt-in, so bench/torque_bench.exs needs no change.
The rustler crate was pinned at 0.36 while the Elixir side had moved to 0.38. Nothing enforced the match anymore (rustler 0.38 no longer raises unsupported_rustler_version), so the drift went unnoticed. Both sides are now on 0.38; no API changes were needed. Also refreshes Cargo.lock: sonic-number 0.1.1 -> 0.1.3, sonic-simd 0.1.3 -> 0.1.4, serde 1.0.229, thiserror 2.0.20, plus transitives. Build, clippy and cargo fmt are clean and the suite passes. Benchmarks show no change attributable to the bump: run-to-run variance on a plain fat-LTO build (large decode 676 / 535 / 720 ips across three runs of the same binary) exceeds any effect.
One run of bench/torque_bench.exs on PGO builds of both torque and glazer 1.0.1, rebuilt on the updated deps. Also documents the llvm-profdata merge step the glazer PGO recipe needs: its Makefile writes the flow for GCC (-fprofile-correction, *.gcda), so under clang `make PGO=use` fails on a missing default.profdata until the raw counters are merged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Elixir
mix.lockrefresh: benchee 1.5.1, dialyxir 1.4.8, ex_doc 0.40.4, jiffy 2.0.2, stream_data 1.4.0~> 0.5->~> 1.0; 0.5.15 is retired on hexglazer 1.0 keeps everything the benchmarks use (
compile_path/1,find/2,validate_utf8,force_utf8) and UTF-8 validation is still opt-in, sobench/torque_bench.exsneeds no change.Rust
unsupported_rustler_version), so the drift went unnoticed. No source changes were needed.Cargo.lockrefresh: sonic-number 0.1.1 -> 0.1.3, sonic-simd 0.1.3 -> 0.1.4, serde 1.0.229, thiserror 2.0.20, itoa 1.0.18, bytes 1.12.1, plus transitives.Verification
cargo build --release,cargo clippy -- -D warnings,cargo fmt --check: cleanTORQUE_BUILD=true mix test: 309 passed, 1 skipped