Skip to content
ai-llm-inference logo

AI LLM Inference

ai-llm-inference

Operational patterns for LLM inference: latency budgeting, tail-latency control, caching, batching/scheduling, quantization/compression, parallelism, and reliable serving at scale. Emphasizes production-grade performance, cost control, and observability.

SKILL.md

Full skill instructions

LLMOps - Inference & Optimization - Production Skill Hub

Modern Best Practices (January 2026):

This skill provides production-ready operational patterns for optimizing LLM inference performance, cost, and reliability. It centralizes decision rules, optimization strategies, configuration templates, and operational checklists for inference workloads.

No theory. No narrative. Only what Codex can execute.


When to Use This Skill

Codex should activate this skill whenever the user asks for:

  • Optimizing LLM inference latency or throughput
  • Choosing quantization strategies (FP8/​FP4/​INT8/​INT4)
  • Configuring vLLM, TensorRT-LLM, or DeepSpeed inference
  • Scaling LLM inference across GPUs (tensor/​pipeline parallelism)
  • Building high-throughput LLM APIs
  • Improving context window performance (KV cache optimization)
  • Using speculative decoding for faster generation
  • Reducing cost per token
  • Profiling and benchmarking inference workloads
  • Planning infrastructure capacity
  • CPU/​edge deployment patterns
  • High availability and resilience patterns

Scope Boundaries (Use These Skills for Depth)


Quick Reference

TaskTool/​FrameworkCommand/​PatternWhen to Use
Latency budgetSLO + load modelTTFT/​ITL + P95/​P99 under loadAny production endpoint
Tail-latency controlScheduling + timeoutsAdmission control + queue caps + backpressurePrevent p99 explosions
ThroughputBatching + KV-cache aware servingContinuous batching + KV pagingHigh concurrency serving
Cost controlModel tiering + cachingCache (prefix/​response) + quotasReduce spend and overload risk
Long contextPrefill optimizationChunked prefill + prompt compressionLong inputs and RAG-heavy apps
ParallelismTP/​PP/​DPChoose by model size and interconnectModels that do not fit one device
ReliabilityResilience patternsTimeouts + circuit breakers + idempotencyAvoid cascading failures

Decision Tree: Inference Optimization Strategy

Need to optimize LLM inference: [Optimization Path]
    │
    ├─ High throughput (>10k tok/​s) OR P99 variance > 3x P50?
    │   └─ YES -> Disaggregated inference (prefill/​decode separation)
    │            See references/​disaggregated-inference.md
    │
    ├─ Primary constraint: Throughput?
    │   ├─ Many concurrent users? -> batching + KV-cache aware serving + admission control
    │   ├─ Chat/​agents with KV reuse? -> SGLang (RadixAttention)
    │   └─ Mostly batch/​offline? -> batch inference jobs + large batches + spot capacity
    │
    ├─ Primary constraint: Cost?
    │   ├─ Can accept lower quality tier? -> model tiering (small/​medium/​large router)
    │   └─ Must keep quality? -> caching + prompt/​context reduction before quantization
    │
    ├─ Primary constraint: Latency?
    │   ├─ Draft model acceptable? -> speculative decoding
    │   └─ Long context? -> prefill optimizations + FlashAttention-3 + context budgets
    │
    ├─ Large model (>70B)?
    │   ├─ Multiple GPUs? -> Tensor parallelism (NVLink required)
    │   └─ Deep model? -> Pipeline parallelism (minimize bubbles)
    │
    ├─ Hardware selection?
    │   ├─ Memory-bound? -> more HBM, higher bandwidth
    │   ├─ Latency-bound? -> faster clocks + kernel support
    │   └─ Multi-node? -> prioritize interconnect (NVLink/​RDMA) and topology
    │
    │   Notes: treat GPU/​SKU advice as time-sensitive; verify with vendor docs and your own benchmarks.
    │   See references/​gpu-optimization-checklists.md and references/​infrastructure-tuning.md
    │
    └─ Edge deployment?
        └─ CPU + quantization -> llama.cpp/​GGUF for constrained resources

Intake Checklist (REQUIRED)

Before recommending changes, collect (or infer) these inputs:

  • Model + variant (size, context length, precision/​quantization, tokenizer)
  • Traffic shape (prompt/​output length distributions, concurrency, QPS, streaming vs non-streaming)
  • SLOs and budgets (TTFT/​ITL/​total latency targets, error budget, cost per request)
  • Serving stack (engine/​version, batching/​scheduling settings, caching, parallelism, autoscaling)
  • Hardware and topology (GPU type/​count, VRAM, NVLink/​RDMA, CPU/​RAM, storage, cluster/​runtime)
  • Constraints (quality floor, safety requirements, rollout/​rollback constraints)

Core Concepts & Practices

Core Concepts (Vendor-Agnostic)

  • Latency components: queueing + prefill + decode; optimize the largest contributor first.
  • Tail latency: p99 is dominated by queuing and long prompts; fix with admission control and context budgets.
  • Retries: retries can multiply load; bound retries and use hedged requests only with strict budgets.
  • Caching: prefix caching helps repeated system/​tool scaffolds; response caching helps repeated questions (requires invalidation).
  • Security & privacy: prompts/​outputs can contain sensitive data; scrub logs, enforce auth/​tenancy, and rate-limit abuse (OWASP LLM Top 10: https://owasp.org/www-project-top-10-for-large-language-model-applications/).

Implementation Practices (Tooling Examples)

  • Measure under load: benchmark TTFT/​ITL and p95/​p99 with realistic concurrency and prompt lengths.
  • Separate environments: dev/​stage/​prod model configs; promote only after passing the inference review checklist.
  • Export telemetry: request-level tokens, TTFT/​ITL, queue depth, GPU memory headroom, and error classes (OpenTelemetry GenAI semantic conventions: https://opentelemetry.io/docs/specs/semconv/gen-ai/).

Do / Avoid

Do

  • Do enforce max_input_tokens and max_output_tokens at the API boundary.
  • Do cap concurrency and queue depth; return overload errors quickly.
  • Do validate quality after any quantization or kernel change.

Avoid

  • Avoid unbounded retries (amplifies outages).
  • Avoid unbounded context windows (OOM + latency spikes).
  • Avoid benchmarking on single requests; always test with realistic concurrency.

Accuracy Protocol (REQUIRED)

  • Treat performance ratios (for example, "2x faster") as hypotheses unless a source is cited and the workload is comparable.
  • Do not recommend hardware/​SKU changes without stating assumptions (model size, context length, concurrency, interconnect).
  • Prefer a measured baseline + checklist-driven rollout over "best practice" claims.

Resources (Detailed Operational Guides)

For comprehensive guides on specific topics, see:

Infrastructure & Serving

Performance Optimization

Deployment & Operations


Templates

Inference Configs

Production-ready configuration templates for leading inference engines:

Quantization & Compression

Model compression templates for reducing memory and cost:

Serving Pipelines

High-throughput serving architectures:

Caching & Batching

Performance optimization templates:

Benchmarking

Performance measurement and validation:

Checklists

Navigation

Resources

Templates

Data


Trend Awareness Protocol

IMPORTANT: When users ask recommendation questions about LLM inference, you MUST use WebSearch to check current trends before answering.

Trigger Conditions

  • "What's the best inference engine for [use case]?"
  • "What should I use for [serving/​quantization/​batching]?"
  • "What's the latest in LLM inference optimization?"
  • "Current best practices for [vLLM/​TensorRT/​quantization]?"
  • "Is [inference tool] still relevant in 2026?"
  • "[vLLM] vs [TensorRT-LLM] vs [SGLang]?"
  • "Best quantization method for [model size]?"
  • "What GPU should I use for inference?"

Required Searches

  1. Search: "LLM inference optimization best practices 2026"
  2. Search: "[vLLM/​TensorRT-LLM/​SGLang] comparison 2026"
  3. Search: "LLM quantization trends January 2026"
  4. Search: "LLM serving new releases 2026"

What to Report

After searching, provide:

  • Current landscape: What serving engines are popular NOW (not 6 months ago)
  • Emerging trends: New inference optimizations gaining traction
  • Deprecated/​declining: Techniques or tools losing relevance
  • Recommendation: Based on fresh data, not just static knowledge

Example Topics (verify with fresh search)

  • Inference engines (vLLM 0.7+, TensorRT-LLM, SGLang, llama.cpp)
  • Quantization methods (FP8, AWQ, GPTQ, GGUF, bitsandbytes)
  • Attention kernels (FlashAttention-3, FlashInfer, xFormers)
  • Speculative decoding advances
  • KV cache optimization techniques
  • New GPU architectures (H200, Blackwell) and their optimizations

Related Skills

This skill focuses on inference-time performance. For related workflows:

  • See "Scope Boundaries" above.

External Resources

See data/​sources.json for:

  • Serving frameworks (vLLM, TensorRT-LLM, DeepSpeed-MII)
  • Quantization libraries (GPTQ, AWQ, bitsandbytes, LLM Compressor)
  • FlashAttention, FlashInfer, xFormers
  • GPU hardware guides and optimization docs
  • Benchmarking frameworks and tools

Use this skill whenever the user needs LLM inference performance, cost reduction, or serving architecture guidance.

More skills from majiayu000

xiaohongshu logo
majiayu000/claude-arsenal

xiaohongshu

xiaohongshu

286 148
View
agent-task-conductor logo
majiayu000/claude-skill-registry

agent-task-conductor

Conduct multi-agent task orchestration and workflow coordination.

663 1
View
conductor-setup logo
majiayu000/claude-skill-registry

conductor-setup

Initialize project with Conductor artifacts (product definition,

663 1
View
animation-designer logo
majiayu000/claude-skill-registry

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS

663 1
View
diagramming logo
majiayu000/claude-skill-registry

diagramming

Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...

663 1
View
h3-pg logo
majiayu000/claude-skill-registry-data

h3-pg

PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.

23 1
View
conductor-development logo
majiayu000/claude-skill-registry

conductor-development

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...

663 1
View
conductor-status logo
majiayu000/claude-skill-registry

conductor-status

Display project status, active tracks, and next actions

663 1
View
dockerization logo
majiayu000/claude-skill-registry

dockerization

Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.

663 1
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View