🤖 AI Summary
Serverless cold-start latency has long been treated as a black-box performance optimization challenge. Method: This paper reframes it as a developer-visible software design problem, systematically analyzing root causes across design, packaging, and runtime layers using 81 real-world open-source projects. It establishes a taxonomy of initialization anti-patterns and corresponding refactoring strategies, introduces SCABENCH—a dedicated cold-start benchmark—and INITSCOPE, a lightweight static-dynamic analysis framework that precisely correlates code loading with execution paths. Contribution/Results: Empirical evaluation shows INITSCOPE improves root-cause localization accuracy by 40% and reduces diagnosis time by 64% on SCABENCH. Developer studies confirm significant gains in diagnostic accuracy and efficiency. The work fundamentally shifts cold-start mitigation from low-level tuning to a diagnosable, refactorable software design concern and delivers the first systematic, developer-oriented analysis infrastructure for serverless initialization.
📝 Abstract
Serverless computing simplifies deployment and scaling, yet cold-start latency remains a major performance bottleneck. Unlike prior work that treats mitigation as a black-box optimization, we study cold starts as a developer-visible design problem. From 81 adjudicated issue reports across open-source serverless systems, we derive taxonomies of initialization anti-patterns, remediation strategies, and diagnostic challenges spanning design, packaging, and runtime layers. Building on these insights, we introduce SCABENCH, a reproducible benchmark, and INITSCOPE, a lightweight analysis framework linking what code is loaded with what is executed. On SCABENCH, INITSCOPE improved localization accuracy by up to 40% and reduced diagnostic effort by 64% compared with prior tools, while a developer study showed higher task accuracy and faster diagnosis. Together, these results advance evidence-driven, performance-aware practices for cold-start mitigation in serverless design. Availability: The research artifact is publicly accessible for future studies and improvements.