188宝金博页面版

Recovery Oriented Computing (ROC): Motivation, Definition, Techniques, and Case Studies Abstract It is time to broaden our performance-dominated research agenda. A four order of magnitude increase in performance since the first ASPLOS means that few outside CS&E research community believe that speed is the only problem of computer hardware and software. Current systems crash and freeze so frequently that people become violent. 1 Fast but flaky should not be our 21 st century legacy. Recovery Oriented Computing (ROC) takes the perspective that hardware faults, software bugs, and operator errors are facts to be coped with, not problems to be solved. By concentrating on Mean Time to Repair (MTTR) rather than Mean Time to Failure (MTTF), ROC reduces recovery time and thus offers higher availability. Since a large portion of system administration is dealing with failures, ROC may also reduce total cost of ownership. One to two orders of magnitude reduction in cost mean that the purchase price of hardware and software is now a small part of the total cost of ownership. In addition to giving the motivation and definition of ROC, we introduce failure data for Internet sites that shows that the leading cause of outages is operator error. We also demonstrate five ROC techniques in five case studies, which we hope will influence designers of architectures and operating systems. If we embrace availability and maintainability, systems of the future may compete on recovery performance rather than just SPEC performance, and on total cost of ownership rather than just system price. Such a change may restore our pride in the architectures and operating systems we craft. 2 1. Motivation The focus of researchers and developers for the 20 years since the first ASPLOS conference has been performance, and that single-minded effort has yielded a 12,000-fold improvement [HP02]. Key to this success has been benchmarks, which measure progress and reward the winners. 1 A Mori survey in Britain found that more than 12% have seen their colleagues bully the IT department when things go wrong, while 25% of under 25 year olds have seen peers kicking their computers. Some 2% claimed to have actually hit the person next to them in their frustration. HCI Prof. Helen Petrie says, "… it starts in the mind, then becomes physical, with shaking, eyes dilating, sweating, and increased heart rate. You are preparing to have a fight, with no one to fight against." From Net effect of computer rage, by Mark Hughes-Morgan, AP, 2/25/02. 2 Dear Reviewer: Similar to the OceanStore paper at the last ASPLOS, this paper is early in the project, but lays out the perspectives and has initial results to demonstrate importance and plausibility of these potentially controversial ideas. We note that the Call for Papers says ``New-idea'' papers are encouraged; the program committee recognizes that such papers may contain a significantly less thorough evaluation than papers in more established areas. The committee will also give special consideration to controversial papers that stimulate interesting debate during the committee meeting. We hope our novel perspective can offset the lack of performance measurements on a single, integrated prototype.