GPT OSS model on GCP C4 #3107
Open
GPT OSS model on GCP C4 #3107
Conversation
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
* running gpt-oss on Intel Xeon Signed-off-by: jiqing-feng <[email protected]> * add TTFT image Signed-off-by: jiqing-feng <[email protected]> * add _blog.yml Signed-off-by: jiqing-feng <[email protected]> * minor fix Signed-off-by: jiqing-feng <[email protected]> * fix blog Signed-off-by: jiqing-feng <[email protected]> * fix content Signed-off-by: jiqing-feng <[email protected]> * update thumbnail Signed-off-by: jiqing-feng <[email protected]> * update expert parallelism diagram Signed-off-by: jiqing-feng <[email protected]> * fix model name and model link Signed-off-by: jiqing-feng <[email protected]> * fix result image links Signed-off-by: jiqing-feng <[email protected]> * fix script Signed-off-by: jiqing-feng <[email protected]> * update results Signed-off-by: jiqing-feng <[email protected]> --------- Signed-off-by: jiqing-feng <[email protected]>
Signed-off-by: jiqing-feng <[email protected]>
Signed-off-by: jiqing-feng <[email protected]>
Signed-off-by: jiqing-feng <[email protected]>
|
@kding1 @IlyasMoutawwakil , pls help review, thx very much |
Comment on lines
+174
to
+182
| ## Results | ||
| ### Normalized Throughput per vCPU | ||
| Across batch sizes up to 64, Intel Xeon 6 processor‑powered `C4` consistently outperforms `C3` with a 1.4x ~ 1.7× throughput per-vCPU. The formula is: | ||
|
|
||
| $$normalized\\_throughput\\_per\\_vCPU = (throughput\\_C4 / vCPUs\\_C4) / (throughput\\_C3 / vCPUs\\_C3)$$ | ||
|
|
||
| <kbd> | ||
| <img src="assets/gpt-oss-on-intel-xeon/throughput-gpt-oss-per-vcpu.png"> | ||
| </kbd> |
There was a problem hiding this comment.
would it make sense to also include throughput numbers ? I understand that normalized throughput has increased but I don't see from where to where, as in what throughput should one expect from deployment on this cpu instance.
IlyasMoutawwakil
approved these changes
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This blog shows: Intel Granite Rapids (C4) provides both performance gains and better cost efficiency for large MoE inference than Sapphire Rapids (C3).