Conversation
Track NVIDIA's nightly cuopt-cu12/cuopt-cu13 wheels (26.10 dev channel) instead of the pinned 26.8 stable release, so future builds on this branch stay current with pre-release fixes. This intentionally does not touch gmscuopt.c: the new multi-GPU PDLP feature is not reachable through the C API in any nightly build yet (confirmed by tracing cuOptSolve -> solve_lp_with_method -> run_pdlp, none of which read num_gpus for method=PDLP; distributed dispatch only exists in the mps_data_model-based solve_lp overload used by cuopt_cli, which the C API never calls). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
uv's default index-strategy stops looking once it finds a matching package name on an index, even if no version there satisfies the constraint. Since pypi.nvidia.com only has stable cuopt-cu12/cuopt-cu13 releases (up to 26.8.0), uv found the package there first and refused to fall through to the nightly index for a 26.10.* build, failing resolution. Verified locally (dry-run) that the nightly index alone resolves all cu12/cu13 dependencies for both x86_64 and arm64. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
cuOpt's C API accepts num_gpus up to 72, but the concurrent-mode code path it actually drives (solve.cu) hardcodes the barrier thread to device index 1, so values above 2 are accepted without error but have no further effect. Widen the GAMS option's upper bound to match the C API so it's not artificially more restrictive, and make the description explicit about the 2-GPU cap so users aren't misled into expecting more speedup from higher values. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Track NVIDIA's nightly cuopt-cu12/cuopt-cu13 wheels (26.10 dev channel) instead of the pinned 26.8 stable release, so future builds on this branch stay current with pre-release fixes. This intentionally does not touch gmscuopt.c: the new multi-GPU PDLP feature is not reachable through the C API in any nightly build yet (confirmed by tracing cuOptSolve -> solve_lp_with_method -> run_pdlp, none of which read num_gpus for method=PDLP; distributed dispatch only exists in the mps_data_model-based solve_lp overload used by cuopt_cli, which the C API never calls).