Topic

vLLM

All digests tagged vLLM

AI Engineer Paris 2026 Main Stage: Google DeepMind, ElevenLabs, Hugging Face & Stripe | Day 2 thumbnail

· 8:44:15

AI Engineer Paris 2026 Main Stage: Google DeepMind, ElevenLabs, Hugging Face & Stripe | Day 2

This summary covers advanced topics in production AI systems, focusing on scaling generative media, optimizing LLM inference, and building real-time AI features. Key technical deep dives include customizing generative models (e.g., Flux for action prediction), achieving low-latency speaker diarization, and optimizing model deployment by integrating Hugging Face's `transformers` library into `vLLM`. Furthermore, the talks emphasize that modern AI development requires a global, agent-centric playbook, necessitating localized payments and robust fraud monitoring.

Key takeaways

  1. AI Model Customization is Multi-Layered 23:20

    Customizing models like Flux involves optimizing multiple surfaces: Prompt Upsampling (using VLM/LLM to steer user intent), Moderation (via configurable APIs or embedding into weights using LoRA), and adding new modalities (e.g., Flux Action for robot control).

  2. Optimizing LLM Inference with vLLM 41:40

    The `transformers` modeling backend allows running Hugging Face models directly in `vLLM`, enabling access to advanced features like KV cache, continuous batching, and expert parallelization while maintaining the original model's code base.

  3. Real-Time AI Requires Causal Segmentation 46:40

    Achieving low-latency speaker diarization for voice agents requires moving from batch processing to causal segmentation, which processes audio in streaming chunks to maintain accuracy while minimizing latency (e.g., achieving 400ms latency).

  4. AI Product Playbook Must Be Global and Agent-Ready 50:00

    Successful AI companies must treat their day-one market as the entire world, localizing pricing, payment methods, and adapting their product design to be discoverable and purchasable by AI agents.

Watch on YouTube Full article

Two Bugs That Hid in Plain Sight: A vLLM Debugging Detective Story — Asaf Gardin & Yuval Belfer thumbnail

· 18:06

Two Bugs That Hid in Plain Sight: A vLLM Debugging Detective Story — Asaf Gardin & Yuval Belfer

This talk details two critical, non-crashing bugs found in stateful inference systems (specifically vLLM/Mamba) that manifest as 'gibberish' or logprob spikes. Both issues were surfaced by memory pressure and required advanced debugging techniques, including logprob comparison against baseline frameworks and kernel inspection. The core finding is that stateful inference systems do not fail loudly; they can lie with high confidence.

Key takeaways

  1. Use Logprob Comparison for Quality Assurance 0:05

    When debugging inference issues, compare the logprobs generated by the system under test (e.g., vLLM) against a plain reference implementation (e.g., Hugging Face transformers) to detect subtle divergence in token distributions, even when no explicit error occurs. (5:18)

  2. Stress Test with Resource Constraints 0:03

    To reproduce rare bugs, manipulate system constraints. Starving the GPU by reducing memory utilization (e.g., from 90% to 20%) or increasing the scale of rollouts per prompt can force latent bugs to surface. (3:43)

  3. Thread Identity Through the Forward Pass 0:10

    In complex kernels, identity can be lost when data is reduced to tensors. Propagating a unique request ID through a `forward context` allows engineers to set breakpoints and trace which specific request is executing faulty logic. (10:30)

Watch on YouTube Full article