Conclusions: Availability benchmarks
Our methodology is best for understanding the availability behavior of a system
- extensions are needed to distill results for automated system comparison
A good fault-injection environment is critical
- need realistic, reproducible, controlled faults
- system designers should consider building in hooks for fault-injection and availability testing
Measuring and understanding availability will be crucial in building systems that meet the needs of modern server applications
- our benchmarking methodology is just the first step towards this important goal