Main.Purpose History
Show minor edits - Show changes to output
Changed line 20 from:
<!-- Start of StatCounter Code -->
to:
<!-- Start of StatCounter Code for Default Guide -->
Changed line 22 from:
to:
Changed lines 24-26 from:
var sc_partition=57;
var sc_click_stat=1;
var sc_security="d6ef0c3a";
to:
var sc_security="1c9ec15f";
var scJsHost = (("https:" == document.location.protocol) ?
"https://secure." : "http://www.");
document.write("<sc"+"ript type='text/javascript' src='" +
scJsHost+
"statcounter.com/counter/counter.js'></"+"script>");
Changed lines 31-39 from:
<script type="text/javascript"
src="http://www.statcounter.com/counter/counter.js"></script><noscript><div
class="statcounter"><a title="joomla 1.5 stats"
href="http://www.statcounter.com/joomla/"
target="_blank"><img class="statcounter"
src="http://c.statcounter.com/4932734/0/d6ef0c3a/1/"
alt="joomla 1.5 stats" ></a></div></noscript>
<!-- End of StatCounter Code -->
to:
<noscript><div class="statcounter"><a title="web analytics"
href="http://statcounter.com/" target="_blank"><img
class="statcounter"
src="http://c.statcounter.com/9029614/0/1c9ec15f/0/"
alt="web analytics"></a></div></noscript>
<!-- End of StatCounter Code for Default Guide -->
Deleted line 50:
Changed line 2 from:
The purpose of this archive is to facilitate the design, validation, and comparison of fault-tolerant models and algorithms.c
to:
The purpose of this archive is to facilitate the design, validation, and comparison of fault-tolerant models and algorithms.
Changed line 2 from:
The purpose of this archive is to facilitate the design, validation, and comparison of fault-tolerant models and algorithms.
to:
The purpose of this archive is to facilitate the design, validation, and comparison of fault-tolerant models and algorithms.c
Changed line 11 from:
*the comparison and cross-validation of fault-tolerant model or algorithm across identical trace data sets
to:
*the comparison and cross-validation of a fault-tolerant model or algorithm across identical trace data sets
Added line 6:
*a standard format for failure traces
Changed line 8 from:
*links to complementary traces (for example, workload or application traces)
to:
Added lines 17-50:
(:html:)
<!-- Start of StatCounter Code -->
<script type="text/javascript">
var sc_project=4932734;
var sc_invisible=1;
var sc_partition=57;
var sc_click_stat=1;
var sc_security="d6ef0c3a";
</script>
<script type="text/javascript"
src="http://www.statcounter.com/counter/counter.js"></script><noscript><div
class="statcounter"><a title="joomla 1.5 stats"
href="http://www.statcounter.com/joomla/"
target="_blank"><img class="statcounter"
src="http://c.statcounter.com/4932734/0/d6ef0c3a/1/"
alt="joomla 1.5 stats" ></a></div></noscript>
<!-- End of StatCounter Code -->
(:htmlend:)
(:html:)
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-4677301-2");
pageTracker._trackPageview();
} catch(err) {}</script>
(:htmlend:)
Deleted line 12:
*the incorporation of traces into fault simulators or emulators for model or algorithm evaluation
Added line 14:
*the analysis of the evolution of availability in different systems across long timescales
Changed line 16 from:
*the analysis of the evolution of availability in different systems across long timescales
to:
*the incorporation of traces with a common format into fault simulators or emulators for model or algorithm evaluation
Changed line 11 from:
*the evaluation of the generality of a model or algorithm across different types of resources (e.g. in terms of reliability)
to:
*the evaluation of the generality of a model or algorithm across different types of resources (in terms of reliability or user base, for example)
Changed lines 15-16 from:
*the integration of failure models with other types of models (such as workloads)
to:
*the integration of failure models with other types of models (such as workloads)
*the analysis of the evolution of availability in different systems across long timescales
Changed line 7 from:
*links to complementary (workload) traces
to:
*links to complementary traces (for example, workload or application traces)
Changed lines 1-4 from:
Welcome to the webpage of the Failure Trace Archive.
----
The Failure Trace Archive (FTA) is centralized public repository of availability traces of distributed systems, and tools for their analysis.
to:
The '''Failure Trace Archive''' (FTA) is centralized public repository of availability traces of distributed systems, and tools for their analysis.
Changed lines 1-4 from:
Welcome to the webpage of the Failure Trace Archive.
to:
Welcome to the webpage of the Failure Trace Archive.
Changed line 3 from:
%width=25pct height=25pct% http://fta.inria.fr/apache2-default/pmwiki/pub/logo_inria.gif
to:
Added lines 1-21:
Welcome to the webpage of the Failure Trace Archive.
%width=25pct height=25pct% http://fta.inria.fr/apache2-default/pmwiki/pub/logo_inria.gif
----
The Failure Trace Archive (FTA) is centralized public repository of availability traces of distributed systems, and tools for their analysis.
The purpose of this archive is to facilitate the design, validation, and comparison of fault-tolerant models and algorithms.
In particular, the FTA contains the following:
*availability traces of distributed systems, differing in scale, volatility, and usage
*scripts and tools for analyzing these traces
*links to complementary (workload) traces
The FTA allows the following:
*the comparison and cross-validation of fault-tolerant model or algorithm across identical trace data sets
*the evaluation of the generality of a model or algorithm across different types of resources (e.g. in terms of reliability)
*the evaluation the generality of a failure trace, i.e., to determine whether measurements are biased to particular platform or middleware
*the incorporation of traces into fault simulators or emulators for model or algorithm evaluation
*the determination of which trace data set is most interesting or applicable for a given algorithm or model
*the integration of failure models with other types of models (such as workloads)