179 questions
No questions match those filters.
Before deploying a specific model to a specific GPU, ho...
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 plansStart with the memory budget, because a model that doesn’t fit makes every other question moot. Weight memory is roughly 2 bytes per parameter in bf16, or about a quarter of that under INT4 (GPTQ/AWQ); KV-cache memory per sequence depends on layer count, KV-head count, head dimension, and max context length, and it scales with your maximum batch size, not just one request. The check that matters is whether weight memory plus the KV cache at your target maximum batch size stays under roughly 85% of device VRAM, leaving headroom for activations and framework overhead — and if it doesn’t, your levers are quantization, a smaller max batch or context window, or grouped-query attention, which shrinks the KV cache by roughly the ratio of query heads to KV heads and should be close to a default at 7B-plus scale.
Next, latency: decide whether you need continuous batching with paged attention for variable-length concurrent traffic, since naive padding wastes both compute and memory on every shorter sequence in a batch. Then name the compression you’re actually shipping and its measured quality cost on your own evaluation, not its theoretical cost — a perplexity delta, not just “INT8 is usually fine.” Finally, set the autoscaling trigger on a signal that actually predicts saturation, like KV-cache utilization crossing a threshold, rather than raw request count, since the KV cache is usually what runs out first, not compute.