Benchmarking operating system dependability: Windows 2000 as a case study. Kalakech, A; Jarboui, T.; Arlat, J.; Crouzet, Y.; and Kanoun, K. In Proc. of the 10th IEEE Pacific Rim Int'l Symp. on Dependable Computing, pages 261--270, March, 2004.
abstract   bibtex   
We propose a dependability benchmark suitable for a general purpose operating system (OS). The specifications of the benchmark components are presented and illustrated on a benchmark prototype dedicated to Windows 2000. The important novelty, as regards OS dependability benchmarking, is threefold. First, it lies on a comprehensive and structured set of measures: outcomes are considered both at the OS level and at the application level. Second, these measures include not only robustness measures (e.g., the distribution among the observed outcomes for the OS and the application: error codes, exceptions, workload correct or erroneous completion, OS and application hang), but also the related temporal measures in the presence of faults (e.g., system call and workload execution times, as well as operating system restart time). Finally, we are considering a realistic workload (namely, TPC-C client), instead of a synthetic workload.
@inproceedings{kalakech_benchmarking_2004-1,
	title = {Benchmarking operating system dependability: {Windows} 2000 as a case study},
	abstract = {We propose a dependability benchmark suitable for a general purpose operating system (OS). The specifications of the benchmark components are presented and illustrated on a benchmark prototype dedicated to Windows 2000. The important novelty, as regards OS dependability benchmarking, is threefold. First, it lies on a comprehensive and structured set of measures: outcomes are considered both at the OS level and at the application level. Second, these measures include not only robustness measures (e.g., the distribution among the observed outcomes for the OS and the application: error codes, exceptions, workload correct or erroneous completion, OS and application hang), but also the related temporal measures in the presence of faults (e.g., system call and workload execution times, as well as operating system restart time). Finally, we are considering a realistic workload (namely, TPC-C client), instead of a synthetic workload.},
	booktitle = {Proc. of the 10th {IEEE} {Pacific} {Rim} {Int}'l {Symp}. on {Dependable} {Computing}},
	author = {Kalakech, A and Jarboui, T. and Arlat, J. and Crouzet, Y. and Kanoun, K.},
	month = mar,
	year = {2004},
	keywords = {Application software, Benchmark testing, Computer aided software engineering, Computer industry, Councils, Error correction codes, Open source software, Operating systems, Prototypes, Time measurement, Windows 2000, application level, benchmark component specifications, benchmark prototype, fI\_results\_workload\_syscall\_error, fault tolerant computing, fi\_binary, fi\_dbench, fi\_num\_faults\_less\_500, fi\_os, fi\_results\_crash, fi\_results\_hang, fi\_results\_workload\_error, fi\_robusteness, fi\_windows, formal specification, operating system dependability benchmarking, operating systems (computers), realistic workload, robustness, software reliability, user interfaces},
	pages = {261--270}
}
Downloads: 0