logo

Meet Our Experts

Machine Learning Engineer – 2

Mayank Kulkarni Avatar

Authored by


  • vLLM vs SGLang: Why Their Benchmarks Behave So Differently

    AI/ML

    12 mins.

    vLLM vs SGLang: Why Their Benchmarks Behave So Differently

    Explore the vLLM vs SGLang benchmarks to understand performance differences in LLMs and framework comparisons.


  • vLLM or SGLang? Here’s the actual decision guide.

    AI/ML

    5 mins.

    vLLM or SGLang? Here’s the actual decision guide.

    Continuing the series, this one compares between two inference engines, SGLang and vLLM, and provides guidance on choosing the right one based on project requirements. Use this as guide to drive your decisions.


  • If vLLM already solved LLM serving, why did SGLang appear?

    AI/ML

    8 mins.

    If vLLM already solved LLM serving, why did SGLang appear?

    The emergence of vLLM improved GPU utilization for AI model serving, addressing issues like memory fragmentation. However, as workloads evolved towards complex multi-turn interactions, SGLang was developed to optimize prefix caching, reducing unnecessary computations. This ensures higher efficiency, lower latency, and reliable structured outputs such as JSON, enhancing modern AI applications.


  • Why is SGLang booming if vLLM already exists?

    AI/ML

    6 mins.

    Why is SGLang booming if vLLM already exists?

    SGLang and vLLM are two tools developed to enhance the efficiency of using open-source AI models. While vLLM addresses resource wastage in AI model hosting, SGLang improves response times by minimizing repetition in processing requests. Here’s a read to help you decide which one is better.


  • vLLM Solved the Wrong Bottleneck… and That’s Why It Won

    AI/ML

    11 mins.

    vLLM Solved the Wrong Bottleneck… and That’s Why It Won

    This blog discusses inefficiencies in GPU utilization for language model serving due to memory management issues, notably the KV cache. It highlights five core problems that impact throughput and proposes solutions.


  • B300 in Production: What 18 Benchmark Runs Actually Showed 

    AI/ML

    9 mins.

    B300 in Production: What 18 Benchmark Runs Actually Showed 

    We benchmarked five models on the NVIDIA B300 – from Gemma-4-26B to GLM-5.2 at 753 billion parameters, across 18 runs under real production concurrency. The throughput numbers are strong. The TTFT finding is counterintuitive. And the infrastructure implication is bigger than either.