aboutsummaryrefslogtreecommitdiffhomepage
path: root/third_party/protobuf/benchmarks/README.md
diff options
context:
space:
mode:
authorGravatar Jakob Buchgraber <buchgr@google.com>2017-04-12 14:30:38 +0200
committerGravatar Jakob Buchgraber <buchgr@google.com>2017-04-13 14:32:42 +0200
commitea82aa115794b019472b44d4f94ed902c1217f30 (patch)
tree06ace57ced74604ddcfb545632cfc7eb768ff164 /third_party/protobuf/benchmarks/README.md
parente1c31944c3bcc89722a8e77013b11110edf3b5f6 (diff)
protobuf: Update protobuf to @laszlocsomor's master at commit 421d909.
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially the development version of protobuf 3.2.0 and windows specific fixes from laszlo. Those fixes will be merged into protobuf soon: https://github.com/google/protobuf/pull/2969). For instructions on how to update protobuf for bazel see README.bazel.md. Change-Id: I4f663955b0baeea3232b69ce32d9292427f5274a
Diffstat (limited to 'third_party/protobuf/benchmarks/README.md')
-rw-r--r--third_party/protobuf/benchmarks/README.md28
1 files changed, 28 insertions, 0 deletions
diff --git a/third_party/protobuf/benchmarks/README.md b/third_party/protobuf/benchmarks/README.md
new file mode 100644
index 0000000000..c902780582
--- /dev/null
+++ b/third_party/protobuf/benchmarks/README.md
@@ -0,0 +1,28 @@
+
+# Protocol Buffers Benchmarks
+
+This directory contains benchmarking schemas and data sets that you
+can use to test a variety of performance scenarios against your
+protobuf language runtime.
+
+The schema for the datasets is described in `benchmarks.proto`.
+
+Generate the data sets like so:
+
+```
+$ make
+$ ./generate-datasets
+Wrote dataset: dataset.google_message1_proto3.pb
+Wrote dataset: dataset.google_message1_proto2.pb
+Wrote dataset: dataset.google_message2.pb
+$
+```
+
+Each data set will be written to its own file. Benchmarks will
+likely want to run several benchmarks against each data set (parse,
+serialize, possibly JSON, possibly using different APIs, etc).
+
+We would like to add more data sets. In general we will favor data sets
+that make the overall suite diverse without being too large or having
+too many similar tests. Ideally everyone can run through the entire
+suite without the test run getting too long.