ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-24 15:16:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Zooko O'Whielacronx 2007-04-14 18:03:54 -07:00
parent 625f230954
commit b4e25737ff
1 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
pyfec/README.txt
View File

@ -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. 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 * API
Each block is associated with "blocknum". The blocknum of each primary block is 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. 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 * Acknowledgements
Thanks to the author of the original fec lib, Luigi Rizzo, and the folks that Thanks to the author of the original fec lib, Luigi Rizzo, and the folks that