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

Unified Diff: benchmarks/run.html

Issue 6071: Removed the use of Math.random() and new Date() for building... (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/crypto.js ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: benchmarks/run.html
===================================================================
--- benchmarks/run.html (revision 399)
+++ benchmarks/run.html (working copy)
@@ -130,17 +130,22 @@
<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>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 and the use of
+Math.random() and new Date() to build an RNG pool has been
+removed. </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>
+<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/crypto.js ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698