<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GPU Computing | Dylan Chiang</title><link>https://dylanchiang-dev.github.io/en/tags/gpu-computing/</link><atom:link href="https://dylanchiang-dev.github.io/en/tags/gpu-computing/index.xml" rel="self" type="application/rss+xml"/><description>GPU Computing</description><generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-US</language><lastBuildDate>Wed, 22 Oct 2025 00:00:00 +0000</lastBuildDate><image><url>https://dylanchiang-dev.github.io/media/icon_hu_982c5d63a71b2961.png</url><title>GPU Computing</title><link>https://dylanchiang-dev.github.io/en/tags/gpu-computing/</link></image><item><title>Paper reading: Aegaeon - Efficient GPU pooling technology for concurrent LLM services on the market</title><link>https://dylanchiang-dev.github.io/en/post/aegaeon-gpu-pooling/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://dylanchiang-dev.github.io/en/post/aegaeon-gpu-pooling/</guid><description>&lt;p>I recently read an important paper &amp;ldquo;Aegaeon: Effective GPU Pooling for Concurrent LLM Serving on the Market&amp;rdquo; that will be published in SOSP &amp;lsquo;25. This research, completed by Peking University and Alibaba Group, proposes a revolutionary multi-model LLM service system, which greatly improves GPU resource utilization efficiency.&lt;/p>
&lt;h2 id="research-background-and-challenges">Research background and challenges&lt;/h2>
&lt;h3 id="resource-waste-problem-in-the-model-market">Resource waste problem in the model market&lt;/h3>
&lt;p>With the rapid development of large-scale language models, model marketplaces such as Hugging Face now host over a million models. However, there is a serious waste of resources in the actual production environment:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Obvious long tail effect&lt;/strong>: 94.1% of models receive only 1.35% of requests&lt;/li>
&lt;li>&lt;strong>Uneven Resource Allocation&lt;/strong>: 17.7% of the GPU is used to serve a &amp;ldquo;cold&amp;rdquo; model that averages less than 0.2 requests per second&lt;/li>
&lt;li>&lt;strong>Difficult to cope with burst loads&lt;/strong>: &amp;ldquo;Hot&amp;rdquo; models (such as DeepSeek, Llama, Qwen) face request bursts and may exceed reserved resources&lt;/li>
&lt;/ul>
&lt;h3 id="limitations-of-existing-solutions">Limitations of existing solutions&lt;/h3>
&lt;p>Existing GPU pooling solutions mainly fall into two categories:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Multiplexing&lt;/strong>: Limited by GPU memory capacity, supports up to 2-3 models/GPU&lt;/li>
&lt;li>&lt;strong>Auto-scaling&lt;/strong>: Expanding at the request level, there is a head blocking (HOL) problem&lt;/li>
&lt;/ol>
&lt;h2 id="aegaeons-core-innovation">Aegaeon’s Core Innovation&lt;/h2>
&lt;h3 id="token-level-automatic-expansion">Token level automatic expansion&lt;/h3>
&lt;p>The biggest innovation of Aegaeon is the token-level automatic expansion mechanism, which is in contrast to the request-level expansion of existing solutions:&lt;/p>
&lt;p>&lt;strong>Request Level Expansion&lt;/strong>: Must wait for the entire request to complete before switching models
&lt;strong>Token level extension&lt;/strong>: models can be switched predictively during token generation&lt;/p>
&lt;h3 id="separate-scheduling-architecture">Separate scheduling architecture&lt;/h3>
&lt;p>Aegaeon divides the GPU pool into two partitions:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Prefill instance&lt;/strong>: Specially handles the initial processing of input prompts&lt;/li>
&lt;li>&lt;strong>Decoding instance&lt;/strong>: specifically handles subsequent token generation&lt;/li>
&lt;/ol>
&lt;p>This separation avoids the complexity of unified scheduling and enables more balanced resource utilization.&lt;/p>
&lt;h3 id="scheduling-strategy">Scheduling strategy&lt;/h3>
&lt;p>&lt;strong>Prefill phase scheduling&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>Adopt grouped FCFS (First-Come-First-Serve) strategy&lt;/li>
&lt;li>Group requests for the same model, maximum group size is 8&lt;/li>
&lt;li>Prioritize loading into existing groups to reduce over-expansion&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Decoding phase scheduling&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>Use Weighted Round-Robin strategy&lt;/li>
&lt;li>Assign time quotas based on SLO requirements&lt;/li>
&lt;li>Utilize output buffering to hide latency&lt;/li>
&lt;/ul>
&lt;h2 id="system-optimization-technology">System optimization technology&lt;/h2>
&lt;h3 id="component-reuse">Component Reuse&lt;/h3>
&lt;p>Aegaeon significantly reduces initialization overhead by reusing inference engine components:&lt;/p>
&lt;ul>
&lt;li>Distributed actuators (Ray, NCCL)&lt;/li>
&lt;li>Analyze and optimize components&lt;/li>
&lt;li>Tokenizer&lt;/li>
&lt;li>Memory pool&lt;/li>
&lt;/ul>
&lt;h3 id="explicit-memory-management">Explicit memory management&lt;/h3>
&lt;p>&lt;strong>Self-managed VRAM buffer&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>Allocate all necessary VRAM at once&lt;/li>
&lt;li>Use bump allocation strategy to avoid fragmentation&lt;/li>
&lt;li>Bypass the allocation mechanism of the tensor library&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Unified KV Cache&lt;/strong>:&lt;/p>
&lt;ul>
&lt;li>Using slab allocation technology&lt;/li>
&lt;li>Maintain dedicated pool for each shape of KV cache&lt;/li>
&lt;li>Effectively manage memory fragmentation&lt;/li>
&lt;/ul>
&lt;h3 id="fine-grained-kv-cache-synchronization">Fine-grained KV cache synchronization&lt;/h3>
&lt;p>Implementing asynchronous KV cache transfers using CUDA events:&lt;/p>
&lt;ul>
&lt;li>&lt;code>cudaEventRecord&lt;/code>: Log transfer events&lt;/li>
&lt;li>&lt;code>cudaEventQuery&lt;/code>: Query completion status&lt;/li>
&lt;li>&lt;code>cudaStreamWaitEvent&lt;/code>: synchronized execution sequence&lt;/li>
&lt;/ul>
&lt;h2 id="experimental-results-and-performance-evaluation">Experimental results and performance evaluation&lt;/h2>
&lt;h3 id="end-to-end-performance">End-to-end performance&lt;/h3>
&lt;p>Test results on the ShareGPT dataset:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>RPS = 0.1&lt;/strong>: Aegaeon supports 70 models, 2x more than ServerlessLLM&lt;/li>
&lt;li>&lt;strong>RPS = 0.5&lt;/strong>: Aegaeon achieves 2.5x higher request arrival rate&lt;/li>
&lt;li>&lt;strong>Single GPU Efficiency&lt;/strong>: Supports up to 7 models/GPU&lt;/li>
&lt;/ul>
&lt;h3 id="performance-under-strict-slo">Performance under strict SLO&lt;/h3>
&lt;p>Even under stricter SLO requirements:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>0.5× SLO&lt;/strong>: still supports 50% more models than the baseline solution&lt;/li>
&lt;li>&lt;strong>0.3× SLO&lt;/strong>: 12.5% more models supported&lt;/li>
&lt;/ul>
&lt;h3 id="automatic-expansion-speed">Automatic expansion speed&lt;/h3>
&lt;ul>
&lt;li>Near-instant scaling (via prefetching) 50% of the time&lt;/li>
&lt;li>Expansion completes within 1 second in other cases&lt;/li>
&lt;li>KV cache transfer overhead per request is less than 1 second&lt;/li>
&lt;/ul>
&lt;h2 id="production-environment-deployment">Production environment deployment&lt;/h2>
&lt;h3 id="deployment-scale">Deployment scale&lt;/h3>
&lt;p>Aegaeon has been tested and deployed in Alibaba Cloud Model Studio for three months:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>GPU Scale&lt;/strong>: 213 H20 GPUs&lt;/li>
&lt;li>&lt;strong>Number of models&lt;/strong>: 47 models (28 1.8-7B, 19 32-72B)&lt;/li>
&lt;li>&lt;strong>Resource Savings&lt;/strong>: Reduced from 1,192 GPUs to 213 (82% savings)&lt;/li>
&lt;/ul>
&lt;h3 id="actual-performance-improvement">Actual performance improvement&lt;/h3>
&lt;p>GPU utilization improved from an average of 13.3%∼33.9% to 48.1%, with no SLO violations or service interruptions observed during the 70 hours of monitoring.&lt;/p>
&lt;h2 id="summary-of-technical-contributions">Summary of technical contributions&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>Revealing for the first time&lt;/strong> the excessive cost problem of concurrent LLM services in the market&lt;/li>
&lt;li>&lt;strong>The first token-level automatic expansion&lt;/strong> multi-model service solution&lt;/li>
&lt;li>&lt;strong>First comprehensive optimization&lt;/strong> Predictive automatic expansion process, reducing overhead by 97%&lt;/li>
&lt;li>&lt;strong>Real production deployment verification&lt;/strong>, proving the ability to significantly reduce OPEX&lt;/li>
&lt;/ol>
&lt;h2 id="future-development-direction">Future development direction&lt;/h2>
&lt;p>Although Aegaeon has made breakthrough progress, there is still room for improvement in the following areas:&lt;/p>
&lt;ul>
&lt;li>Support larger model clusters&lt;/li>
&lt;li>Optimize performance in extremely low latency scenarios&lt;/li>
&lt;li>Explore combinations with multiplexing technology&lt;/li>
&lt;li>Expand to more diverse hardware platforms&lt;/li>
&lt;/ul>
&lt;h2 id="conclusion">Conclusion&lt;/h2>
&lt;p>Aegaeon represents an important milestone in the design of LLM inference systems. Through token-level automatic expansion and full-stack optimization, it not only solves the resource waste problem faced by the model market, but also provides a technical foundation for the sustainable development of cloud AI services.&lt;/p>
&lt;hr>
&lt;h2 id="-paper-information">📄 Paper information&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Paper Title&lt;/strong>: Aegaeon: Effective GPU Pooling for Concurrent LLM Serving on the Market&lt;/li>
&lt;li>&lt;strong>Authors&lt;/strong>: Yuxing Xiang, Xue Li, Kun Qian, Yufan Yang, Diwen Zhu, Wenyuan Yu, Ennan Zhai, Xuanzhe Liu, Xin Jin, Jingren Zhou&lt;/li>
&lt;li>&lt;strong>Institution&lt;/strong>: Peking University, Alibaba Group&lt;/li>
&lt;li>&lt;strong>Conference&lt;/strong>: ACM SIGOPS 31st Symposium on Operating Systems Principles (SOSP &amp;lsquo;25)&lt;/li>
&lt;li>&lt;strong>Year of Publication&lt;/strong>: 2025&lt;/li>
&lt;li>&lt;strong>DOI&lt;/strong>:
&lt;/li>
&lt;li>&lt;strong>PDF link&lt;/strong>:
&lt;/li>
&lt;/ul></description></item></channel></rss>