llm-deployment

Deploy and serve large language models with vLLM, TGI, Ollama, and Kubernetes.

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/ehadziabdic/WAgents --skill llm-deployment-ehadziabdic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: llm-deployment
Source: https://github.com/ehadziabdic/WAgents/tree/main/opencode/skills/llm-deployment
Command: npx skills add https://github.com/ehadziabdic/WAgents --skill llm-deployment-ehadziabdic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vllm, matplotlib, and includes scripts (resource) and references (resource) components.

What problem does it solve? Serving large language models in production requires specialized infrastructure for continuous batching, KV-cache management, quantization, and GPU scaling, which is difficult to configure correctly without deep operational knowledge. ## Core Features & Use Cases - Multi-Framework Serving: Launch OpenAI-compatible inference endpoints with vLLM, Text Generation Inference, Ollama, or llama.cpp, with guidance on when each fits. - Quantization & Optimization: Apply AWQ, GPTQ, GGUF, and FP8 quantization plus PagedAttention and prefix caching to cut memory usage and raise throughput. - Production Deployment: Generate Docker Compose files and Kubernetes manifests with GPU scheduling, health probes, and autoscaling, plus SageMaker LMI and Bedrock guidance. - Use Case: You need to serve a fine-tuned 70B model to internal users. Use this Skill to pick AWQ quantization, generate a Kubernetes deployment with tensor parallelism across two A100s, and benchmark TTFT and tokens-per-second before going live. ## Quick Start Deploy Llama-3.1-8B-Instruct as an OpenAI-compatible API server using vLLM and then benchmark its latency and throughput.

Frequently Asked Questions about llm-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an LLM with vLLM for production?▼

Install vLLM and run vllm serve with your model ID, tensor-parallel size, GPU memory utilization, and max model length to launch an OpenAI-compatible API server. The included deploy_vllm.py script automates server launch, health checks, and manifest generation.

vLLM vs TGI vs Ollama: which LLM serving framework should I use?▼

vLLM is the default for production GPU serving with PagedAttention and continuous batching. TGI fits Hugging Face hub workflows, Ollama suits local development with one-command setup, and llama.cpp targets CPU and edge inference.

How much GPU memory does a 70B model need for inference?▼

A 70B model needs about 140 GB in FP16, 70 GB in FP8, or roughly 38-40 GB with 4-bit AWQ/GPTQ quantization, plus 1-4 GB of KV cache per concurrent request. Two A100 80GB GPUs with tensor parallelism handle a 4-bit 70B deployment.

Why does my SageMaker LMI endpoint fail to detect the model engine?▼

This happens when configuration is passed only via environment variables and the model lives in a tarball subdirectory, so DJL's root scan finds nothing. Place a serving.properties file at the tarball root with option.model_id pointing to the model subdirectory.

When is self-hosting an LLM cheaper than using API providers?▼

Self-hosting becomes cost-effective above roughly 50-100M tokens per month for 70B models, or 10-20M per month for 7-13B models, assuming over 50% GPU utilization. Below that, managed APIs like Bedrock avoid GPU provisioning and on-call overhead.