aboutsummaryrefslogtreecommitdiff
path: root/benchmarks
diff options
context:
space:
mode:
authorYilun Chong <yilunchong@google.com>2018-01-02 09:57:04 -0800
committerYilun Chong <yilunchong@google.com>2018-01-02 09:57:04 -0800
commita147a213764e0a34e0c0edf9fddaeb6aa608bd0d (patch)
treeea5a1342914c988c37ca518e4abdf7c0d1b8dba2 /benchmarks
parent4b0209140ea3155b78960d2fe3f62062c1c098a6 (diff)
downloadprotobuf-a147a213764e0a34e0c0edf9fddaeb6aa608bd0d.tar.gz
protobuf-a147a213764e0a34e0c0edf9fddaeb6aa608bd0d.tar.bz2
protobuf-a147a213764e0a34e0c0edf9fddaeb6aa608bd0d.zip
Changed README
Diffstat (limited to 'benchmarks')
-rw-r--r--benchmarks/README.md23
1 files changed, 12 insertions, 11 deletions
diff --git a/benchmarks/README.md b/benchmarks/README.md
index 9621053f..09c06907 100644
--- a/benchmarks/README.md
+++ b/benchmarks/README.md
@@ -22,7 +22,17 @@ We're using maven to build the java benchmarks, which is the same as to build
the Java protobuf. There're no other tools need to install. We're using
[google/caliper](https://github.com/google/caliper) as benchmark tool, which
can be automaticly included by maven.
-
+
+### Big data
+
+There's some optional big testing data which is not included in the directory initially, you need to
+run the following command to download the testing data:
+
+```
+$ ./download_data.sh
+```
+
+After doing this the big data file will automaticly generated in the benchmark directory.
## Run instructions
@@ -46,7 +56,7 @@ For java:
```
$ make java-benchmark
-$ ./java-benchmark $(specific generated dataset file name)
+$ ./java-benchmark $(specific generated dataset file name) [-- $(caliper option)]
```
For cpp:
@@ -58,15 +68,6 @@ $ ./cpp-benchmark $(specific generated dataset file name)
## Benchmark datasets
-There's some optional big testing data which is not included in the directory initially, you need to
-run the following command to download the testing data:
-
-```
-$ ./download_data.sh
-```
-
-After doing this the big data file will automaticly generated in the benchmark directory.
-
Each data set is in the format of benchmarks.proto:
1. name is the benchmark dataset's name.