A Case for an Open Source Data Repository.pptVIP

A Case for an Open Source Data Repository Archana Ganapathi Department of EECS, UC Berkeley (archanag@) Why do we study failure data? Understand cause-effect relationship between configurations and system behavior Still don’t have a complete understanding of failures in systems Can’t worry about fixing problems if we don’t understand them in the first place Gauge behavioral changes over time Need realistic workload/faultload data to test/evaluate systems Success stories…people have benefited from failure data analysis Crash data collection success stories Berkeley EECS BOINC 2 Unnamed Companies …So Why Does Windows Crash? Definitions Crash Event caused by a problem in the operating system(OS) or application(app) Requires OS or app restart. Application Crash A crash occurring at user-level, caused by one or more components (.exe/.dll files) Requires an application restart. Application Hang An application crash caused as a result of the user terminating a process that is potentially deadlocked or running an infinite loop. Component (.exe/.dll file routing) causing the loop/deadlock cannot be identified (yet) OS Crash A crash occurring at kernel-level, caused by memory corruption, bad drivers or faulty system-level routines. Blue-screen-generating crashes require a machine reboot Windows explorer crashes require restarting the explorer process. Bluescreen An OS crash that produces a user-visible blue screen followed by a non-optional machine reboot. Procedure Collect crash dumps from two different sources UC Berkeley EECS department BOINC volunteers Filter data/form crash clusters to avoid double-counting Account for shared resources, dependent processes, system instability, user retry Parse/Interpret crash dumps using Debugging tools for Windows Study both application crash behavior and operating systems crashes Supplement crash data with usage data EECS Dataset Crashes reported per month Usage/Crashes per day of week Usage/Crashes per hour of day Reboot Fr