Hibernation Testing Challenges and Optimization Opportunities
summary
Hibernation validation runs thousands of cycles and each cycle can take days; CPU online/offline steps cost ~100–200 ms and ~70–100 ms per core so limit CPUs during save reduces suspend time on a 128‑core box by roughly 60% (saves about a minute per cycle, shown on 1,500-cycle estimates). Other changes: delay swap signature removal until after resume to allow retries instead of discarding the image, and an optional backup swap offset to preserve images for fast repro and debugging.
AI-written summary · about
chapters (7)
- 0:00Introduction to hibernation
- 1:46Hibernation testing challenges
- 3:56Optimization opportunities
- 5:45CPU online offline delays
- 7:10Fault tolerance in hibernation
- 9:18Debugging improvements
- 10:42Q&A and conclusion
related talks
47mIs Linux Suspend ready for the next decade
48mExtending the swsusp Hibernation Framework to ARM
32mCPU Power Saving Methods for Real-time Workloads
29mA Hidden Cost of Virtualization When Scaling Multicore Applications
19mDo nothing fast: How to scale idle cpus?
30mHost and Guest Suspend Under Xen - S3 and S0ix
30mHow to get realistic c-state latency and residency?
59mDevice power management and idle