Skip to content

add random range ratio that is appropriate#402

Merged
cquil11 merged 1 commit intofeat/mi355x-disaggfrom
fix/random-range-mi355x-disagg
Jan 7, 2026
Merged

add random range ratio that is appropriate#402
cquil11 merged 1 commit intofeat/mi355x-disaggfrom
fix/random-range-mi355x-disagg

Conversation

@cquil11
Copy link
Collaborator

@cquil11 cquil11 commented Jan 7, 2026

This is a followup to https://github.com/InferenceMAX/InferenceMAX/pull/348 .

This PR referenced another repo that called the benchmark serving script without the appropriate random range ratio. Here are the associated changes (comparing to the original branch): https://github.com/billishyahao/sglang_disagg/pull/8/changes. Note that since I do not have write access to the upstream sglang_disagg repository, I changed to my fork in this PR. But you can see the changes above.


Note

Introduces a new runtime parameter and updates the source repo for the benchmark job launcher.

  • Require and forward RANDOM_RANGE_RATIO via check_env_vars and as an argument to submit_disagg.sh
  • Change sglang_disagg clone URL to https://github.com/cquil11/sglang_disagg.git (branch sa-260107)

Written by Cursor Bugbot for commit 82e555f. This will update automatically on new commits. Configure here.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @cquil11, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates a new RANDOM_RANGE_RATIO parameter into the sglang-disagg benchmarking process. This change involves updating the benchmark script to expect and pass this ratio, and it also switches the source repository for sglang_disagg to a specific fork that likely supports this new functionality, ensuring the benchmarks run with the intended random range behavior.

Highlights

  • New Environment Variable: Introduced and validated a new environment variable, RANDOM_RANGE_RATIO, which is now expected to be set for the benchmark script.
  • Benchmark Parameter Update: The newly introduced RANDOM_RANGE_RATIO is passed as an additional parameter to the submit_disagg.sh script, indicating its use in the benchmark execution.
  • Repository Source Change: The sglang_disagg repository cloned by the benchmark script has been updated to point to cquil11's fork, suggesting that this fork contains the necessary implementations for the new RANDOM_RANGE_RATIO functionality.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@cquil11 cquil11 merged commit b8f8004 into feat/mi355x-disagg Jan 7, 2026
1 check passed
@cquil11 cquil11 deleted the fix/random-range-mi355x-disagg branch January 7, 2026 19:29
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds support for the RANDOM_RANGE_RATIO environment variable to the Slurm benchmark script. The variable is now checked for existence and passed to the submit_disagg.sh script. The change also updates the git repository URL for sglang_disagg. My review includes one suggestion to clean up a duplicated variable in the environment check.

PREFILL_NUM_WORKERS PREFILL_TP PREFILL_EP PREFILL_DP_ATTN \
DECODE_NUM_WORKERS DECODE_TP DECODE_EP DECODE_DP_ATTN \
PREFILL_NODES DECODE_NODES SGL_SLURM_JOBS_PATH # SGL_SLURM_JOBS_PATH FIXME
PREFILL_NODES DECODE_NODES SGL_SLURM_JOBS_PATH RANDOM_RANGE_RATIO SGL_SLURM_JOBS_PATH
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The SGL_SLURM_JOBS_PATH variable is listed twice in the call to check_env_vars. This is redundant and likely a copy-paste error. Please remove the duplicate entry for better code clarity.

Suggested change
PREFILL_NODES DECODE_NODES SGL_SLURM_JOBS_PATH RANDOM_RANGE_RATIO SGL_SLURM_JOBS_PATH
PREFILL_NODES DECODE_NODES SGL_SLURM_JOBS_PATH RANDOM_RANGE_RATIO

PREFILL_NUM_WORKERS PREFILL_TP PREFILL_EP PREFILL_DP_ATTN \
DECODE_NUM_WORKERS DECODE_TP DECODE_EP DECODE_DP_ATTN \
PREFILL_NODES DECODE_NODES SGL_SLURM_JOBS_PATH # SGL_SLURM_JOBS_PATH FIXME
PREFILL_NODES DECODE_NODES SGL_SLURM_JOBS_PATH RANDOM_RANGE_RATIO SGL_SLURM_JOBS_PATH
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate SGL_SLURM_JOBS_PATH in environment variable check

Low Severity

SGL_SLURM_JOBS_PATH appears twice in the check_env_vars call. The original line had a comment # SGL_SLURM_JOBS_PATH FIXME that was accidentally converted into actual code when adding RANDOM_RANGE_RATIO. While this won't break the script (the variable is just checked twice), it's clearly unintentional duplication from removing the comment incorrectly.

Fix in Cursor Fix in Web

cquil11 added a commit that referenced this pull request Jan 8, 2026
* Revert "Revert "[AMD] Add mi355x distributed inference test CI workflow (#348)" (#400) [skip-sweep]"

This reverts commit a075f2e.

* add random range ratio that is appropriate (#402)

* comment out 1k8k 8k1k

* change recipe back to upstream

* revert comment out 1k8k 8k1k

* Add empty line at the beginning of the script

---------

Co-authored-by: billishyahao <[email protected]>
cquil11 added a commit that referenced this pull request Jan 8, 2026
* add random range ratio that is appropriate (#402)

* comment out 1k8k 8k1k

* change recipe back to upstream

* revert comment out 1k8k 8k1k

* Add empty line at the beginning of the script

---------

Co-authored-by: billishyahao <[email protected]>
Co-authored-by: ichbinblau [email protected]
Co-authored-by: Duyi-Wang [email protected]
Co-authored-by: inkcherry [email protected]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

1 participant