summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPatrick Simianer <p@simianer.de>2014-07-13 15:41:14 +0200
committerPatrick Simianer <p@simianer.de>2014-07-13 15:41:14 +0200
commita7b9b43b310e9987a1056c5828acba9fc928740a (patch)
tree670c5af9ddbef8a9ba5b1b35ea2d5979b7519380
parent35b21b7456743096f84027f8005babe8afbfa0cd (diff)
readme
-rw-r--r--README.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/README.md b/README.md
index d8e2d64..d1c1ea5 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@ Serializer Benchmark
Comparing parsing speed/memory usage of all C++ JSON libs I could find. Also including two msgpack implementations (C++/Ruby).
Goal is to output object.edges.last.rule.substr(1, 4).
Data are fairly large and complex objects (hypergraph representations) with a lot of different types, e.g. strings (ASCII), ints, floats, arrays
-and sub-objects.
+and sub-objects. Download data here [4] and put in the data/ directory.
Note that the comparison is unfair for some parsers, as they just do SAX-style parsing and do not actually fill "real" objects
with data (e.g. the cdec json parser).
@@ -46,6 +46,7 @@ Versions:
* [1] https://github.com/redpony/cdec/tree/master/decoder
* [2] http://fossil.wanderinghorse.net/repos/nosjob/index.cgi/index
* [3] https://github.com/pks/scripts
+* [4] http://simianer.de/serializer_benchmark_data.tar.gz
Results