Sep 2026· Proceedings of the International Conference on Parallel Processing· 0 citations· 4 references
TL;DR
MIGServe treats the physical layout of MIG instances as a first-class scheduling dimension through three techniques: buddy-aware partition placement, which preserves large contiguous free blocks by allocating next to existing occupied buddies; proactive pair-matching migration, which consolidates fragmented half-full buddy pairs off the critical path of inference.
Abstract
NVIDIA’s Multi-Instance GPU (MIG) technology partitions a single GPU into hardware-isolated instances of varying sizes, offering a promising substrate for serving Large Language Model (LLM) workloads with dynamic request profiles. However, existing MIG management approaches suffer from high resource fragmentation and reconfiguration overhead. The root cause is that they treat GPU resources as scalar capacities, while MIG enforces a buddy-aligned physical layout in which instances must occupy contiguous slices and can only be reshaped along fixed boundaries. This mismatch raises three challenges: (i) a layout-oblivious small instance acts as a roadblock that prevents adjacent free blocks from coalescing; (ii) stochastic request lifetimes scatter instances across the layout, accumulating fragmentation; and (iii) under skewed traffic, evicting a temporarily idle hot instance for a sporadic cold request triggers an evict-then-reload cycle. We present MIGServe, a layout-aware MIG resource management system that enables fine-grained dynamic reconfiguration for LLM serving. MIGServe treats the physical layout of MIG instances as a first-class scheduling dimension through three techniques: (1) buddy-aware partition placement, which preserves large contiguous free blocks by allocating next to existing occupied buddies; (2) proactive pair-matching migration, which consolidates fragmented half-full buddy pairs off the critical path of inference; and (3) temperature-guided eviction, which shields hot instances from transient cold requests to suppress reconfiguration thrashing. On NVIDIA A100 GPUs with production-inspired LLM workloads, MIGServe serves 2.38 × –5.32 × more requests under 90% SLO attainment, reduces fragmentation by 52.9%–100%, and cuts reconfiguration overhead by 81.7%–100% over state-of-the-art methods.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
The ongoing work building a Raspberry Pi cluster consisting of 300 nodes is presented, with potential use cases being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.
P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al.· IEEE International Conferenc...· 110 citations· ⚡7
The results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains, and 219 factors representing causes of unhappiness while developing software are identified.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· International Conference on...· 84 citations· ⚡6
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.