Skip to content

fix: correct output multipliers for all previous Azure OpenAI models + docs 7d→30d#29

Merged
msftnadavbh merged 2 commits intomainfrom
fix/ptu-multiplier-and-docs
Feb 12, 2026
Merged

fix: correct output multipliers for all previous Azure OpenAI models + docs 7d→30d#29
msftnadavbh merged 2 commits intomainfrom
fix/ptu-multiplier-and-docs

Conversation

@msftnadavbh
Copy link
Copy Markdown
Owner

Summary

Fixes the output_multiplier for all "Previous Azure OpenAI models" in the PTU sizing calculator, and updates the CLI data-collection script time window.

Changes

PTU Multiplier Fixes (ptu_models.py)

All four "Previous Azure OpenAI models" had output_multiplier = 4 — should be 3.

Model Before After Verification
gpt-4o 4 3 Foundry calculator: RPM=444, in=917, out=250 → 300 PTUs (only works with 3×)
gpt-4o-mini 4 3 Official MS docs example table: RPM=1000, prompt=5000, completion=50 → 140 PTUs (only works with 3×; 4× gives 145)
o3-mini 4 3 Same "previous model" category; docs: "older models use a different ratio"
o1 4 3 Same "previous model" category; docs: "older models use a different ratio"

Sources:

Docs Update (USAGE_EXAMPLES.md)

Changed the CLI data-collection script time window from 7 days → 30 days for more representative workload sizing.

Testing

All 150 tests pass (56 PTU-specific tests).

… o1)

gpt-4o-mini: verified via official MS docs example table on latency page
  (RPM=1000, prompt=5000, completion=50 → 140 PTUs only works with 3×)
o3-mini, o1: same 'previous model' category; docs state 'older models
  use a different ratio' — aligned with verified models.

gpt-4o was already fixed in prior commit (verified via Foundry calculator).
@msftnadavbh msftnadavbh merged commit 83301f3 into main Feb 12, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant