Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(444)

Unified Diff: benchmarks/run.html

Issue 4401: Introduce some checks to indicate that the benchmarks have run correctly.... (Closed) Base URL: http://v8.googlecode.com/svn/branches/bleeding_edge/
Patch Set: '' Created 12 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « benchmarks/richards.js ('k') | benchmarks/run.js » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: benchmarks/run.html
===================================================================
--- benchmarks/run.html (revision 362)
+++ benchmarks/run.html (working copy)
@@ -18,8 +18,10 @@
margin:1em 0
}
-h1,h2,h3,h4{margin-bottom:0}
-h1{font-size:160%}
+h1,h2,h3,h4{margin:0; margin-bottom:0}
+h1{font-size: 200%; height: 2em}
+h2{font-size: 140%; height: 2em}
+h3{font-size: 100%; height: 2em}
li{
margin:.3em 0 1em 0;
@@ -41,12 +43,6 @@
margin-bottom: 20px;
}
-h1 {
- margin: 0px;
- font-size: 24.5px;
- height: 29.35px;
-}
-
td.contents {
text-align: start;
}
@@ -121,6 +117,30 @@
<li><b>EarleyBoyer</b><br/>Classic Scheme benchmarks, translated to JavaScript by Florian Loitsch's Scheme2Js compiler (<i>4682 lines</i>).</li>
</ul>
+<div class="title"><h2>Revisions of the benchmark suite</h2></div>
+
+<p><i>Please note that benchmark results are not comparable unless both
+results are run with the same revision of the benchmark suite. We will be
+making revisions from time to time in order to fix bugs or expand the scope
+of the benchmark suite.</i></p>
+
+<div class="title"><h3>Version 1</h3></div>
+
+<p>Initial release.</p>
+
+<div class="title"><h3>Version 2</h3></div>
+
+<p>For version 2 the crypto benchmark was fixed. Previously, the decryption
+stage was given plaintext as input, which resulted in an error. Now, the
+decryption stage is given the output of the encryption stage as input. The
+result is checked against the original plaintext. For this to give the correct
+results the crypto objects are reset for each iteration of the benchmark. In
+addition, the size of the plain text has been increased a little.</p>
+
+<p>Other benchmarks were fixed to do elementary verification of the results of
+their calculations. This is to avoid accidentally obtaining scores that are
+the result of an incorrect JavaScript engine optimization.</p>
+
</td><td style="text-align: center">
<div class="run">
<div id="status" style="text-align: center; margin-top: 75px; font-size: 120%; font-weight: bold;">Starting...</div>
« no previous file with comments | « benchmarks/richards.js ('k') | benchmarks/run.js » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698