179 questions
No questions match those filters.
How do you deploy open-source LLMs to production using...
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansvLLM has become the default choice for serving open-weight models like Llama or Mistral because of two specific engineering wins over naive serving: PagedAttention manages the KV cache in fixed-size pages instead of contiguous blocks, which eliminates the memory fragmentation that limits how many requests naive serving can hold in memory at once, and continuous batching lets new requests join a batch mid-flight instead of waiting for the whole batch to finish, which is what actually unlocks serving dozens of concurrent requests instead of one.
A realistic deployment path starts with sizing hardware to the model — a 7B model comfortably fits on a single mid-range GPU, while a 70B model typically needs multiple high-memory GPUs unless quantization is applied. Techniques like AWQ or GPTQ quantization cut memory requirements roughly four-fold, which can be the difference between needing four GPUs and needing one. From there it’s standard infrastructure: containerize the vLLM server with the model weights, deploy on a GPU-aware Kubernetes node pool with autoscaling tied to queue depth, and run multiple replicas behind a load balancer for availability.