protobuf/benchmarks
2016-09-23 11:07:45 -07:00
..
benchmark_messages_proto2.proto Added C++ benchmark. (#1525) 2016-09-23 11:07:45 -07:00
benchmark_messages_proto3.proto Added C++ benchmark. (#1525) 2016-09-23 11:07:45 -07:00
benchmarks.proto Addressed PR comments. 2016-05-03 12:53:49 -07:00
cpp_benchmark.cc Added C++ benchmark. (#1525) 2016-09-23 11:07:45 -07:00
generate_datasets.cc Addressed PR comments. 2016-05-03 12:53:49 -07:00
google_message1.dat Update benchmark data. 2009-03-05 23:16:14 +00:00
google_message2.dat Initial benchmarking. 2009-03-05 11:00:49 +00:00
google_size.proto More cleanup, based around searches for "Google.ProtocolBuffers" 2015-06-26 20:13:07 +01:00
Makefile.am Added C++ benchmark. (#1525) 2016-09-23 11:07:45 -07:00
ProtoBench.java Replace links to code.google.com/protobuf with developers.google.com/protocol-buffers 2014-10-01 16:26:23 -07:00
README.md Added README describing the directory. 2016-04-27 18:34:33 -07:00
readme.txt benchmarks: update readme.txt 2016-08-26 18:11:44 -07:00

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.