Skip to content

kimik2.5-fp4-b300-vllm: bump vLLM image to v0.22.0 and expand concurrency sweep - #1674

Merged
functionstackx merged 6 commits into
mainfrom
kimik2.5-fp4-b300-vllm-image-v0.22.0
Jun 7, 2026
Merged

kimik2.5-fp4-b300-vllm: bump vLLM image to v0.22.0 and expand concurrency sweep#1674
functionstackx merged 6 commits into
mainfrom
kimik2.5-fp4-b300-vllm-image-v0.22.0

Conversation

@RohitNagraj

@RohitNagraj RohitNagraj commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

Two changes to kimik2.5-fp4-b300-vllm:

  1. vLLM image bumpvllm/vllm-openai:v0.21.0vllm/vllm-openai:v0.22.0.
  2. Concurrency sweep — for both the 1k/1k and 8k/1k cells: TP4/EP1 conc 4-641-128, TP8/EP1 conc-start 41 (conc-end 4 unchanged).

Appends a perf-changelog entry.


Note

Low Risk
Benchmark-only YAML and changelog updates; no runtime application or auth/data-path changes, though wider sweeps increase benchmark run time and cost.

Overview
Updates the kimik2.5-fp4-b300-vllm benchmark recipe in nvidia-master.yaml: the vLLM container moves from v0.21.0 to v0.22.0, and the fixed-seq-len concurrency sweeps for the 1k/1k and 8k/1k cells are widened so low-concurrency points are included and TP4 can be searched up to 128 concurrent requests (previously TP4 started at 4 and capped at 64; TP8 now sweeps from 1 through 4 instead of starting at 4).

A matching perf-changelog.yaml entry documents the image bump and sweep changes for kimik2.5-fp4-b300-vllm.

Reviewed by Cursor Bugbot for commit 014787e. Bugbot is set up for automated code reviews on this repo. Configure here.

Update the kimik2.5-fp4-b300-vllm vLLM image from v0.21.0 to v0.22.0.
Appends a perf-changelog entry.
…m-image-v0.22.0

# Conflicts:
#	perf-changelog.yaml

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Additional findings (outside current diff — PR may have been updated during review):

  • 🔴 perf-changelog.yaml:3478-3482 — The new perf-changelog entry has two issues to fix before merge: (1) pr-link is still the literal placeholder https://github.com/SemiAnalysisAI/InferenceX/pull/<TODO> (the PR description acknowledges this) — should be /pull/1674. (2) The file no longer ends with a trailing newline (\ No newline at end of file in the diff), breaking the line-termination pattern AGENTS.md flags as load-bearing for this file.

    Extended reasoning...

    Bug 1: <TODO> placeholder in pr-link

    The newly appended entry in perf-changelog.yaml (lines 3478–3482) ends with:

      pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/<TODO>

    Every other entry in the file uses a real numeric PR number (e.g. /pull/1544, /pull/1647, /pull/1648, /pull/1663). The PR description itself explicitly notes this: "documenting the image update (PR link still <TODO>)". The result is a dead URL in the changelog pointing to https://github.com/SemiAnalysisAI/InferenceX/pull/<TODO>, which is not a valid GitHub PR.

    Fix: replace <TODO> with 1674 (this PR's number).

    Bug 2: Missing trailing newline at EOF

    The diff shows \ No newline at end of file immediately after the new entry. AGENTS.md is explicit about this file:

    perf-changelog.yaml — benchmark trigger log; append-only; preserve whitespace.

    Never delete or modify whitespace in perf-changelog.yaml — CI depends on exact whitespace (including trailing spaces on blank separator lines). Altering it breaks CI.

    Before this PR the file ended with ...pull/1544\n (trailing newline preserved). After this PR it ends with the bytes ...pull/<TODO> with no terminator. Every prior entry in the file is followed by a newline plus a blank separator line before the next entry begins.

    Step-by-step proof

    1. Check the previous file termination (HEAD~1): tail -c 50 perf-changelog.yaml | od -c shows p u l l / 1 5 4 4 \n.
    2. After this PR's diff is applied, the same command shows p u l l / < T O D O > with no \n.
    3. Visit https://github.com/SemiAnalysisAI/InferenceX/pull/<TODO> in a browser → 404, not a real PR.
    4. If a follow-up PR appends another entry without first restoring the newline, the YAML stream will concatenate as pull/<TODO>- config-keys: on a single line, producing a malformed entry.

    Impact

    • The changelog contains a broken URL that should point to PR #1674.
    • The whitespace deviation contradicts AGENTS.md's load-bearing guidance for this exact file, and sets up the next appended entry to produce a malformed line concatenation.
    • YAML parsing itself still succeeds today (yaml.safe_load tolerates a missing trailing newline), so this is unlikely to break CI immediately, but it violates the documented convention and the file's consistent pattern.

    Fix

    - config-keys:
        - kimik2.5-fp4-b300-vllm
      description:
        - "Update vLLM image from v0.21.0 to v0.22.0"
      pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/1674

    …followed by a trailing newline (and ideally the same blank-separator-line pattern used between prior entries).

@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

TP4/EP1 conc 4-64 -> 1-128 and TP8/EP1 conc-start 4 -> 1 for the
1k/1k and 8k/1k cells. Appends a perf-changelog entry.
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

@RohitNagraj RohitNagraj changed the title kimik2.5-fp4-b300-vllm: bump vLLM image to v0.22.0 kimik2.5-fp4-b300-vllm: bump vLLM image to v0.22.0 and expand concurrency sweep Jun 5, 2026
@functionstackx

Copy link
Copy Markdown
Collaborator

/reuse-sweep-run

@functionstackx
functionstackx merged commit 81b019c into main Jun 7, 2026
4 of 6 checks passed
@functionstackx
functionstackx deleted the kimik2.5-fp4-b300-vllm-image-v0.22.0 branch June 7, 2026 00:10
@github-actions

github-actions Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Development

Successfully merging this pull request may close these issues.

2 participants