@conference {1374610,
	title = {Towards an I/O tracing framework taxonomy},
	booktitle = {PDSW {\textquoteright}07: Proceedings of the 2nd international workshop on Petascale data storage},
	year = {2007},
	pages = {56{\textendash}62},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {There is high demand for I/O tracing in High Performance Computing (HPC). It enables in-depth analysis of distributed applications and file system performance tuning. It also aids distributed application debugging. Finally, it facilitates collaboration within and between government, industrial, and academic institutions by enabling the generation of replayable I/O traces, which can be easily distributed and anonymized as necessary to protect confidential or sensitive information. As a response to this demand for tracing tools, various means of I/O trace generation exist. We first survey the I/O Tracing Framework landscape, exploring three popular such frameworks: LANL- Trace [3], Tracefs [1], and //TRACE1 [2].
We next develop an I/O Tracing Framework taxonomy. The purpose of this taxonomy is to assist I/O Tracing Framework users in formalizing their tracing requirements, and to provide the developers of I/O Tracing Frameworks a language to categorize the functionality and performance of them. The taxonomy categorizes I/O Tracing Framework features such as the type of data captured, trace replayability, and anonymization. The taxonomy also considers elapsed-time overhead and performance overhead. Finally, we provide a case study in the use of our new taxonomy, revisiting all three I/O Tracing Frameworks explored in our survey, to formally classify the features of each.},
	isbn = {978-1-59593-899-2},
	doi = {http://doi.acm.org/10.1145/1374596.1374610},
	author = {Andy Konwinski and Bent, John and Nunez, James and Quist, Meghan}
}
