docs(ms-ai-architect): KB-refresh MEDIUM 6/33 — multi-turn: RPM/TPM-forhold varierer per modell (6 RPM/1K kun eldre chat)
This commit is contained in:
parent
b94fdb0d53
commit
14c71ff7a0
1 changed files with 2 additions and 2 deletions
|
|
@ -1,6 +1,6 @@
|
|||
# Multi-Turn Conversation and Context Management
|
||||
|
||||
**Last updated:** 2026-02
|
||||
**Last updated:** 2026-06-24
|
||||
**Status:** GA
|
||||
**Category:** Prompt Engineering & LLM Optimization
|
||||
|
||||
|
|
@ -312,7 +312,7 @@ AgentSession resumedSession = await agent.DeserializeSessionAsync(serializedSess
|
|||
- Prompt tokens + `max_tokens` parameter + `best_of` parameter
|
||||
- **Ikke** identisk med billing token count
|
||||
|
||||
**RPM (Requests-Per-Minute)** er koblet til TPM: **6 RPM per 1K TPM**.
|
||||
**RPM (Requests-Per-Minute)** er koblet til TPM, men **forholdet varierer per modell**. For eldre chat-modeller (gpt-4o-klassen) er det **6 RPM per 1K TPM**; reasoning-modeller bruker andre forhold (f.eks. o3 og o4-mini: 1 RPM/1K TPM; o3-mini, o1-mini og o3-pro: 1 RPM/10K TPM; o1: 1 RPM/6K TPM).
|
||||
|
||||
**Best practices:**
|
||||
- Implementer exponential backoff ved 429-errors
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue