setup: add valgrind version to show-tool-versions

[tahoe-lafs/zfec.git] / zfec / README.txt

diff --git a/zfec/README.txt b/zfec/README.txt
index 49fac551c7cc82319e212fbff5b373bc35dfabaf..8c3b51f36ef1a6b746b6c4f8b3a707c4a2679377 100644 (file)
--- a/zfec/README.txt
+++ b/zfec/README.txt
@@ -118,7 +118,7 @@ Note that if 7z is used for archiving then it also does compression, so you
 don't need a separate compressor in that case.
 
 
- * Performance Measurements
+ * Performance
 
 On my Athlon 64 2.4 GHz workstation (running Linux), the "zfec" command-line
 tool encoded a 160 MB file with m=100, k=94 (about 6% redundancy) in 3.9
@@ -139,6 +139,14 @@ 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.
 
+Here is a paper analyzing the performance of various erasure codes and their
+implementations, including zfec:
+
+http://www.usenix.org/events/fast09/tech/full_papers/plank/plank.pdf
+
+Zfec shows good performance on different machines and with different values of
+K and M. It also has a nice small memory footprint.
+
 
  * API
 
@@ -255,11 +263,11 @@ Richard M. Stallman) and Valgrind (starting with Julian Seward) for a pair of
 excellent tools.  Thanks to my coworkers at Allmydata -- http://allmydata.com --
 Fabrice Grinda, Peter Secor, Rob Kinninmont, Brian Warner, Zandr Milewski,
 Justin Boreta, Mark Meras for sponsoring this work and releasing it under a Free
-Software licence.
+Software licence. Thanks to Jack Lloyd, Samuel Neves, and David-Sarah Hopwood.
 
 
 Enjoy!
 
 Zooko Wilcox-O'Hearn
-2008-01-20
+2010-05-24
 Boulder, Colorado