openrouter-performance-tuning
Provides benchmarking tools to measure TTFT and latency, helping you select the fastest models for your production needs.
Install
mkdir -p .claude/skills/openrouter-performance-tuning && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4791" && unzip -o skill.zip -d .claude/skills/openrouter-performance-tuning && rm skill.zipInstalls to .claude/skills/openrouter-performance-tuning
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Optimize OpenRouter request latency and throughput. Use when buildingKey capabilities
- →Benchmark model latency using p50 and p95 metrics
- →Stream completions to reduce time-to-first-token
- →Execute parallel requests with concurrency control
- →Optimize connection settings for throughput
- →Quantify performance improvements from tuning
How it works
It provides a benchmarking harness to measure request round-trip times and offers patterns for streaming and asynchronous execution to improve perceived speed.
Inputs & outputs
When to use openrouter-performance-tuning
- →Measure latency differences between model providers
- →Optimize request throughput for real-time apps
- →Determine p95 latency for production SLAs
- →Validate performance of small models vs large models
About this skill
OpenRouter Performance Tuning
Overview
OpenRouter adds minimal overhead (~50-100ms) to direct provider calls. Most latency comes from the upstream model. Key levers: model selection (smaller = faster), streaming (lower TTFT), parallel requests, prompt size reduction, and provider routing to faster infrastructure. This skill covers benchmarking, streaming optimization, concurrent processing, and connection tuning.
Prerequisites
- An OpenRouter API key (
sk-or-v1-...) exported asOPENROUTER_API_KEY— see theopenrouter-install-authskill for setup - Python 3.8+ with the OpenAI SDK (
openaipackage) — the examples use both the syncOpenAIclient andAsyncOpenAIfor parallel processing - Credits on the key if you benchmark paid models like
anthropic/claude-3.5-sonnet; a:freemodel is enough to validate the benchmark harness itself HTTP-Referer/X-Titleheader values for your app (set in every client constructor here)
Instructions
- Establish a baseline: run
benchmark_model()from Benchmark Latency against your candidate models (e.g.openai/gpt-4o-minivsanthropic/claude-3.5-sonnet) and record p50/p95. - Check the results against the Model Speed Tiers table to confirm each candidate sits in the right tier for your latency budget (200-500ms TTFT fastest tier; 5-30s for reasoning models).
- Switch user-facing paths to
stream_completion()per Streaming for Lower TTFT and verifyttft_msdrops (typically 2-10x). - Move batch workloads to
parallel_completions()per Parallel Request Processing, capping concurrency withasyncio.Semaphore(max_concurrent=5-10). - Apply Connection Optimization — one shared client with
timeout=30.0andmax_retries=2instead of a new client per request. - Work through the Performance Optimization Checklist (set
max_tokens, shrink prompts, consider:nitrovariants and provider routing), then re-run the benchmark to quantify each change.
Benchmark Latency
import os, time, statistics
from openai import OpenAI
client = OpenAI(
base_url="https://openrouter.ai/api/v1",
api_key=os.environ["OPENROUTER_API_KEY"],
default_headers={"HTTP-Referer": "https://my-app.com", "X-Title": "my-app"},
)
def benchmark_model(model: str, prompt: str = "Say hello", n: int = 5) -> dict:
"""Benchmark a model's latency over N requests."""
latencies = []
for _ in range(n):
start = time.monotonic()
response = client.chat.completions.create(
model=model,
messages=[{"role": "user", "content": prompt}],
max_tokens=50,
)
latencies.append((time.monotonic() - start) * 1000)
return {
"model": model,
"p50_ms": round(statistics.median(latencies)),
"p95_ms": round(sorted(latencies)[int(len(latencies) * 0.95)]),
"avg_ms": round(statistics.mean(latencies)),
"min_ms": round(min(latencies)),
"max_ms": round(max(latencies)),
}
# Compare fast vs slow models
for model in ["openai/gpt-4o-mini", "anthropic/claude-3-haiku", "anthropic/claude-3.5-sonnet"]:
result = benchmark_model(model)
print(f"{result['model']}: p50={result['p50_ms']}ms p95={result['p95_ms']}ms")
Streaming for Lower TTFT
def stream_completion(messages, model="openai/gpt-4o-mini", **kwargs):
"""Stream response for lower time-to-first-token."""
start = time.monotonic()
first_token_time = None
full_content = []
stream = client.chat.completions.create(
model=model, messages=messages, stream=True,
stream_options={"include_usage": True}, # Get token counts at end
**kwargs,
)
for chunk in stream:
if chunk.choices and chunk.choices[0].delta.content:
if first_token_time is None:
first_token_time = (time.monotonic() - start) * 1000
full_content.append(chunk.choices[0].delta.content)
total_time = (time.monotonic() - start) * 1000
return {
"content": "".join(full_content),
"ttft_ms": round(first_token_time or 0),
"total_ms": round(total_time),
}
Parallel Request Processing
import asyncio
from openai import AsyncOpenAI
async def parallel_completions(prompts: list[str], model="openai/gpt-4o-mini",
max_concurrent=10, **kwargs):
"""Process multiple prompts concurrently."""
semaphore = asyncio.Semaphore(max_concurrent)
client = AsyncOpenAI(
base_url="https://openrouter.ai/api/v1",
api_key=os.environ["OPENROUTER_API_KEY"],
default_headers={"HTTP-Referer": "https://my-app.com", "X-Title": "my-app"},
)
async def process(prompt):
async with semaphore:
response = await client.chat.completions.create(
model=model,
messages=[{"role": "user", "content": prompt}],
**kwargs,
)
return response.choices[0].message.content
return await asyncio.gather(*[process(p) for p in prompts])
# 10 requests in parallel instead of sequential
results = asyncio.run(parallel_completions(
["Summarize: " + text for text in documents],
max_concurrent=5,
max_tokens=200,
))
Performance Optimization Checklist
| Optimization | Impact | Effort |
|---|---|---|
| Use streaming | TTFT drops 2-10x | Low |
| Use smaller models for simple tasks | 2-5x faster | Low |
| Reduce prompt size | Proportional to reduction | Medium |
Set max_tokens | Caps response time | Low |
| Parallel requests | N requests in ~1 request time | Medium |
Use :nitro variant | Faster inference (where available) | Low |
| Provider routing to fastest | 10-30% latency reduction | Low |
| Connection keep-alive | Saves TCP/TLS handshake | Low |
Model Speed Tiers
| Speed | Models | Typical TTFT |
|---|---|---|
| Fastest | openai/gpt-4o-mini, anthropic/claude-3-haiku | 200-500ms |
| Fast | openai/gpt-4o, google/gemini-2.0-flash-001 | 500ms-1s |
| Standard | anthropic/claude-3.5-sonnet | 1-3s |
| Slow | openai/o1, reasoning models | 5-30s |
Connection Optimization
# Reuse client instance (connection pooling)
# BAD: creating new client per request
for prompt in prompts:
c = OpenAI(base_url="https://openrouter.ai/api/v1", ...) # New TCP connection each time
c.chat.completions.create(...)
# GOOD: reuse single client
client = OpenAI(
base_url="https://openrouter.ai/api/v1",
api_key=os.environ["OPENROUTER_API_KEY"],
timeout=30.0, # Set appropriate timeout
max_retries=2, # Built-in retry with backoff
default_headers={"HTTP-Referer": "https://my-app.com", "X-Title": "my-app"},
)
for prompt in prompts:
client.chat.completions.create(...) # Reuses HTTP connection
Output
- A latency benchmark table per model from
benchmark_model():p50_ms,p95_ms,avg_ms,min_ms,max_msover N sample requests - Streaming metrics from
stream_completion(): the fullcontentplusttft_msandtotal_msfor each request - A list of completions from
parallel_completions()produced in roughly one request's wall-clock time instead of N sequential round-trips - A prioritized tuning plan drawn from the Performance Optimization Checklist (lever, expected impact, effort)
Examples
Benchmark two fastest-tier candidates before committing to one:
for model in ["openai/gpt-4o-mini", "anthropic/claude-3-haiku"]:
r = benchmark_model(model, n=5)
print(f"{r['model']}: p50={r['p50_ms']}ms p95={r['p95_ms']}ms avg={r['avg_ms']}ms")
# openai/gpt-4o-mini: p50=430ms p95=610ms avg=455ms
# anthropic/claude-3-haiku: p50=395ms p95=580ms avg=418ms
Both land in the fastest tier (200-500ms typical TTFT), so choose on cost or quality — then stream_completion() cuts perceived latency further for user-facing paths. More worked examples: references/examples.md.
Error Handling
| Error | Cause | Fix |
|---|---|---|
| High TTFT (>5s) | Model cold-starting or overloaded | Switch to :nitro variant or different provider |
| Timeout errors | max_tokens too high or model too slow | Reduce max_tokens; use streaming; increase timeout |
| Throughput bottleneck | Sequential processing | Use async + semaphore for concurrent requests |
| Inconsistent latency | Provider load varies | Use provider.order to pin to fastest provider |
Enterprise Considerations
- Benchmark models in your infrastructure, not just locally -- network path matters
- Use streaming for all user-facing requests to minimize perceived latency
- Set
max_tokenson every request to bound response time and cost - Reuse client instances to benefit from HTTP connection pooling
- Use
asyncio.Semaphoreto control concurrency and avoid overwhelming the API - Monitor P95 latency, not just average -- tail latencies indicate provider issues
- Consider
:nitromodel variants for latency-critical paths
References
- Examples | Errors
- Models API | Streaming
When not to use it
- →When benchmarking models without sufficient credits
- →When the application does not support streaming
Prerequisites
Limitations
- →Benchmark results depend on local network conditions
- →High concurrency may hit API rate limits
How it compares
This method provides quantitative performance data to inform model selection, rather than relying on anecdotal speed observations.
Compared to similar skills
openrouter-performance-tuning side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| openrouter-performance-tuning (this skill) | 1 | 27d | Review | Intermediate |
| sentry-rate-limits | 1 | 27d | Caution | Intermediate |
| optimizing-performance | 1 | 2mo | Review | Intermediate |
| azure-monitor-opentelemetry-py | 0 | 29d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
sentry-rate-limits
jeremylongshore
Manage Sentry rate limits and quota optimization. Use when hitting rate limits, optimizing event volume, or managing Sentry costs. Trigger with phrases like "sentry rate limit", "sentry quota", "reduce sentry events", "sentry 429".
optimizing-performance
CloudAI-X
Analyzes and optimizes application performance across frontend, backend, and database layers. Use when diagnosing slowness, improving load times, optimizing queries, reducing bundle size, or when asked about performance issues.
azure-monitor-opentelemetry-py
microsoft
Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation. Triggers: "azure-monitor-opentelemetry", "configure_azure_monitor", "Application Insights", "OpenTelemetry distro", "auto-instrumentation".
klingai-prod-checklist
jeremylongshore
Execute pre-launch production readiness checklist for Kling AI. Use when preparing to deploy video generation to production. Trigger with phrases like 'klingai production', 'kling ai go-live', 'klingai launch checklist', 'deploy klingai'.
ascend-profiling-analysis
Ascend
Analyze Ascend NPU profiling data to identify training performance bottlenecks. Breaks down step-level time into compute, unoverlapped communication, and freetime; within compute, analyzes compute vs memory-bound ratios and cube vs vector utilization to summarize the model's performance bottleneck.
python-performance-optimization
wshobson
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.