From: Zooko O'Whielacronx zooko@zooko.com <zooko@zooko.com>
Date: Sun, 15 Apr 2007 01:03:54 +0000 (+0530)
Subject: pyfec: bump the performance measurement bragging up higher in the README
X-Git-Url: https://git.rkrishnan.org/%5B/%5D%20/uri/%22file:/frontends/FOOURL?a=commitdiff_plain;h=12f2cfe0b937b8626b459e2d66e224187cc83d4c;p=tahoe-lafs%2Fzfec.git

pyfec: bump the performance measurement bragging up higher in the README

darcs-hash:6c2b18506fc5332a31970bb0cad96505b198fc17
---

diff --git a/pyfec/README.txt b/pyfec/README.txt
index bb96d7c..e8523cf 100644
--- a/pyfec/README.txt
+++ b/pyfec/README.txt
@@ -86,6 +86,28 @@ Privacy Guard" for encryption.  It is important to do things in order: first
 package, then compress, then encrypt, then erasure code.
 
 
+ * Performance Measurements
+
+On my Athlon 64 2.4 GHz workstation (running Linux), the "fec" command-line
+tool encoded a 160 MB file with m=100, k=94 (about 6% redundancy) in 3.9
+seconds, where the "par2" tool encoded the file with about 6% redundancy in
+27 seconds.  "fec" encoded the same file with m=12, k=6 (100% redundancy) in
+4.1 seconds, where par2 encoded it with about 100% redundancy in 7 minutes
+and 56 seconds.
+
+The underlying C library in benchmark mode encoded from a file at about 
+4.9 million bytes per second and decoded at about 5.8 million bytes per second.
+
+On Peter's fancy Intel Mac laptop (2.16 GHz Core Duo), it encoded from a file
+at about 6.2 million bytes per second.
+
+On my even fancier Intel Mac laptop (2.33 GHz Core Duo), it encoded from a file
+at about 6.8 million bytes per second.
+
+On my old PowerPC G4 867 MHz Mac laptop, it encoded from a file at about 1.3
+million bytes per second.
+
+
  * API
 
 Each block is associated with "blocknum".  The blocknum of each primary block is
@@ -169,28 +191,6 @@ Python interpreter is also required.  We have tested it with Python v2.4 and
 v2.5.
 
 
- * Performance Measurements
-
-On my Athlon 64 2.4 GHz workstation (running Linux), the "fec" command-line
-tool encoded a 160 MB file with m=100, k=94 (about 6% redundancy) in 3.9
-seconds, where the "par2" tool encoded the file with about 6% redundancy in
-27 seconds.  "fec" encoded the same file with m=12, k=6 (100% redundancy) in
-4.1 seconds, where par2 encoded it with about 100% redundancy in 7 minutes
-and 56 seconds.
-
-The underlying C library in benchmark mode encoded from a file at about 
-4.9 million bytes per second and decoded at about 5.8 million bytes per second.
-
-On Peter's fancy Intel Mac laptop (2.16 GHz Core Duo), it encoded from a file
-at about 6.2 million bytes per second.
-
-On my even fancier Intel Mac laptop (2.33 GHz Core Duo), it encoded from a file
-at about 6.8 million bytes per second.
-
-On my old PowerPC G4 867 MHz Mac laptop, it encoded from a file at about 1.3
-million bytes per second.
-
-
  * Acknowledgements
 
 Thanks to the author of the original fec lib, Luigi Rizzo, and the folks that