feat(routing): Add native solution tracing#1
Merged
Conversation
erickreutz
force-pushed
the
eric/record-routing-solution-trace
branch
from
July 26, 2026 14:52
a7fa9bd to
c579b7f
Compare
erickreutz
force-pushed
the
eric/record-routing-solution-trace
branch
from
July 26, 2026 15:14
c579b7f to
d3a7010
Compare
erickreutz
force-pushed
the
eric/record-routing-solution-trace
branch
from
July 26, 2026 15:31
d3a7010 to
b1ff7f2
Compare
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.
Adds bounded native solution-progress tracing for RoutingModel solves.
enable_solution_tracerecords first, best, and latest objectives and timing, solution and improvement counts, total improvement, and bucketed samples. Every cold or warm solve resets the trace. Reusing the same configuration is idempotent.The callbacks capture shared native state only. Search runs keep the existing no-GVL behavior; Ruby objects are built only by
to_hunder the GVL. The trace is mutex-protected for concurrent reads and explicitly armed only around the two solve entry points.Validated with the full suite (107 tests, 371 assertions), Rice 4.8.0 on Ruby 3.3.10, and current Rice 4.12.0. A 60-solve interleaved benchmark measured 796.87ms untraced versus 797.06ms traced median wall time (0.02% overhead).
No gem release or downstream dependency change.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.