summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2011-03-31 18:17:50 +0100
committerLars Wirzenius <liw@liw.fi>2011-03-31 18:17:50 +0100
commita1a4c559122e7795c62b01abf05dcf5c7d4dc85f (patch)
tree4d9ef85b6ab7cd281c37873f1ad94c0cc36c4f9f /README
parent47d50d6d6c445964797a5097c1b089c0333fc1a1 (diff)
downloadlarch-a1a4c559122e7795c62b01abf05dcf5c7d4dc85f.tar.gz
Update README to have new speed-test example.
Diffstat (limited to 'README')
-rw-r--r--README3
1 files changed, 2 insertions, 1 deletions
diff --git a/README b/README
index 70d3862..3ed8c07 100644
--- a/README
+++ b/README
@@ -74,7 +74,8 @@ I have two scripts to run simplistic benchmarks:
* `codec-speed 1000 no` tests speed of the NodeCodec class,
for encoding tree nodes for on-disk storage.
-* `speed-test` tests insert and lookup speeds in trees.
+* `speed-test` tests insert and lookup speeds in trees. Use a `--keys`
+ settings that is reasonably large, e.g., a million or ten.
You may want to run either or both before and after making any changes,
to see if you're making things better or worse.