1 views collected around this technical thread.
This article explains how Azul's CRaC and ReadyNow technologies differ in approach to accelerating Java application startup, detailing the Java launch process, optimization phases, implementation requirements, and a side‑by‑side comparison of their benefits and trade‑offs.
The DeWu Tech article dissects iOS’s dyld BuildingClosure stage, shows how hash‑collision‑laden selector strings inflate its runtime, and demonstrates that renaming the colliding selectors reduces perfect‑hash iterations, cutting the phase’s duration by roughly 80% and noticeably speeding up app startup.
This article provides a comprehensive guide to speeding up Spring Boot application startup by explaining configuration principles, code‑level interventions, lazy loading, dependency reduction, auto‑configuration exclusion, logging adjustments, compile‑time optimizations, and caching strategies, all illustrated with practical Java examples.
This article explains the CRaC (Coordinated Restore at Checkpoint) technology for Java applications, describing its principles, supported environments, practical steps for enabling it with Spring Boot, and use‑case scenarios that dramatically reduce JVM startup time.
This article walks through a systematic investigation of a slow‑starting Dubbo service built on Spring 3.2, using JProfile to pinpoint costly class‑loading checks, disabling unnecessary annotation processing, and resolving thread‑waiting issues caused by RabbitMQ and other components, ultimately reducing deployment time by about 40%.
This article explains why a pre‑ads loading step is required for Android apps, analyzes the limitations of the current linear startup flow, and details several technical solutions—including system‑API checks, exclusion rules, handler hooking, and initialization reversal—to reliably detect icon‑click launches and reduce startup latency.
This article explains the principles of Spring Boot startup configuration, demonstrates how to intervene using ApplicationContextInitializer, SpringApplicationRunListener, ApplicationRunner, and CommandLineRunner, and provides practical optimization tips such as reducing dependencies, adjusting auto‑configuration, enabling lazy loading, compile‑time optimizations, log level tuning, and caching to speed up application startup.
This article examines the causes of slow startup in large Spring applications, presents visual analysis techniques and a toolbox—including Arthas, JVM Sandbox, Async Profiler, and Spring Startup Analyzer—and provides concrete installation, configuration, and optimization procedures that can reduce startup time by 70‑80% while improving development efficiency and resource utilization.
This article explores the challenges of slow Spring application startup in large Java projects, presents detailed analysis techniques, visualizations, and a suite of tools—including Spring Startup Analyzer, Arthas, and Async Profiler—to identify bottlenecks, and provides step‑by‑step optimization methods such as bean lazy loading, jar slimming, and configuration tweaks that can reduce startup time by up to 80% while improving resource utilization and deployment efficiency.
Learn how to dramatically reduce startup time in large Spring applications by using spring-context-indexer to generate component indexes at compile time, configure Maven or Gradle dependencies, create manual or IDE‑generated index files, support custom annotations, and disable indexing when needed.
This article presents a comprehensive set of techniques—including lazy initialization, deferred database connections, selective auto‑configuration, logging level tuning, JVM parameter tweaks, dependency pruning, bean optimization, JIT settings, class‑path scanning reduction, and DevTools restart—to significantly shorten Spring Boot application startup time, each illustrated with clear code examples.
This article investigates why Sharding-JDBC takes over half of the application startup time to load metadata, explains the role of the max.connections.size.per.query setting, demonstrates how adjusting it speeds up startup, and discusses the trade‑offs and potential dead‑lock risks of increasing the value.
iQIYI’s mobile app reduces video startup latency by preloading data, pre‑decoding frames, pre‑creating player instances, streamlining initialization, optimizing DNS and CDN selection, and employing device‑aware decoding strategies, achieving near‑zero launch times and superior user experience while planning further audio‑track and hardware collaborations.
This article details a ten‑month iOS startup optimization project for the Sohu Video app, describing measurement methods, ten technical improvements—including dynamic‑to‑static library conversion, load‑method refactoring, binary reordering, and double‑root view architecture—that together reduced launch time by roughly 46% and provides practical code snippets and performance data.
This article explains how to analyze and accelerate SpringBoot startup by profiling with tools like Async Profiler, refactoring heavy business code, leveraging BeanPostProcessor for bean initialization metrics, using Spring's context indexer, and applying lazy initialization to reduce launch time in large Java backend services.
This article details the systematic analysis and optimization of the 58.com Android app’s startup process, covering profiling, componentized task framework, delayed initialization, merging launch and home activities, layout improvements, monitoring tools, and results that achieved roughly a 50% reduction in cold‑start time.
By analyzing thread preemption on low‑end iPhones, this article demonstrates how selecting appropriate GCD queue QoS levels—favoring Utility or Background over User‑Initiated—reduces main‑thread contention, improves launch screen rendering by ~100 ms, and accelerates message list first‑load by up to 1.5 s without altering business logic.
Baidu’s comprehensive low‑end device startup optimization—using a scoring‑based observation system, TTI metrics, automated degradation prevention, high‑performance tools such as UniKV and ABTest lock fixes, and an intelligent scheduling framework—cut cold‑start TTI by over 40% on Android and 30%‑plus on iOS.
After a decade of growth, the iOS app with millions of lines and dozens of third‑party SDKs was re‑architected by converting selected static libraries into dynamic frameworks, employing lazy loading and dependency analysis to reduce download size and improve launch time, while addressing build and compatibility challenges.
This article details Beike's iOS app startup optimization workflow, covering online startup speed measurement, offline performance analysis with a custom profiler, and governance practices such as +load method control, code stripping, and binary reordering to improve launch time and user experience.