<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>large language models on Sadman Kabir Soumik</title>
    <link>https://soumik.blog/tags/large-language-models/</link>
    <description>Recent content in large language models on Sadman Kabir Soumik</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2022, Sadman Kabir Soumik</copyright>
    <lastBuildDate>Sun, 09 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://soumik.blog/tags/large-language-models/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How vLLM Works for Serving Large Language Models</title>
      <link>https://soumik.blog/artificial-intelligence/how_vllm_works_for_serving_llms/</link>
      <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://soumik.blog/artificial-intelligence/how_vllm_works_for_serving_llms/</guid>
      <description>
        
          
            Introduction Serving a large language model, or LLM, is different from calling an ordinary function. A normal function usually receives an input, does some work, and returns one result. An LLM server keeps a large model loaded in memory, accepts many requests, produces one token at a time, and sends partial results back to users while the answer is still being created.
This creates a difficult engineering problem. The model weights use a lot of memory on a graphics processing unit, or GPU.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
