mirror/protobuf-go
1
0
Fork 0
mirror of https://github.com/protocolbuffers/protobuf-go.git synced 2025-01-01 11:58:21 +00:00
Code Issues Packages Projects Releases Wiki Activity
Go support for Google's protocol buffers
402 Commits 1 Branch 27 Tags 20 MiB
Go 99.8%
Shell 0.2%
a80229e4ed
Go to file
Damien Neil a80229e4ed proto: add benchmark using protobuf repo test data 
The primary (cross-language) protobuf repository contains benchmark data
sets. Add benchmarks using this data. (A version of this benchmark exists
in the protobuf repository, but it uses the v1 API and isn't trivial to
get working.)

Fetch the small benchmark datasets from the
github.com/protocolbuffers/protobuf repo by default. Add a
download_benchdata.bash script which fetches the larger datasets as
well.

Generate necessary packages under internal/testprotos/benchmarks.

To run:

  go run ./proto -bench=BenchmarkData

Usual caveats about benchmarking apply: While these benchmarks use
realistic data, isolated microbenchmarking of proto operations is not
necessarily representitive of performance in production systems.

Change-Id: I58d107554baf104568c86997b5ad50be8b2a5790
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/183297
Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>
2019-06-20 20:38:50 +00:00
cmd cmd/protoc-gen-go: un-deprecate enum maps 2019-06-20 19:36:37 +00:00
compiler/protogen compiler/protogen: rename shadowed path package variables 2019-06-01 01:34:16 +00:00
encoding cmd/protoc-gen-go: un-deprecate enum maps 2019-06-20 19:36:37 +00:00
internal proto: add benchmark using protobuf repo test data 2019-06-20 20:38:50 +00:00
proto proto: add benchmark using protobuf repo test data 2019-06-20 20:38:50 +00:00
reflect cmd/protoc-gen-go: un-deprecate enum maps 2019-06-20 19:36:37 +00:00
runtime internal/fileinit: remove package 2019-06-20 19:35:23 +00:00
testing/prototest reflect/protoreflect: add alternative message reflection API 2019-06-17 17:33:24 +00:00
types cmd/protoc-gen-go: un-deprecate enum maps 2019-06-20 19:36:37 +00:00
.gitignore cmd/protoc-gen-go/testdata: ignore go.sum 2019-03-11 20:19:03 +00:00
.travis.yml .travis.yml: configure for OSX 2019-03-13 18:04:08 +00:00
AUTHORS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
CONTRIBUTING.md CONTRIBUTING.md: add pre-push hook instructions 2018-08-07 23:58:41 +00:00
CONTRIBUTORS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
download_benchdata.bash proto: add benchmark using protobuf repo test data 2019-06-20 20:38:50 +00:00
go.mod internal/fileinit: remove package 2019-06-20 19:35:23 +00:00
go.sum internal/fileinit: remove package 2019-06-20 19:35:23 +00:00
integration_test.go proto: add benchmark using protobuf repo test data 2019-06-20 20:38:50 +00:00
LICENSE AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
PATENTS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
README.md CONTRIBUTING.md: initial commit 2018-08-01 20:39:06 +00:00
regenerate.bash internal/cmd/generate-protos: generate test for testdata 2019-03-11 19:40:53 +00:00
test.bash internal/cmd/generate-protos: generate test for testdata 2019-03-11 19:40:53 +00:00

README.md

Next Generation Go Protocol Buffers

WARNING: This repository is in active development. There are no guarantees about API stability. Breaking changes will occur until a stable release is made and announced.

This repository is for the development of the next major Go implementation of protocol buffers. This library makes breaking API changes relative to the existing Go protobuf library. Of particular note, this API aims to make protobuf reflection a first-class feature of the API and implements the protobuf ecosystem in terms of reflection.

Design Documents

List of relevant design documents:

Contributing

We appreciate community contributions. See CONTRIBUTING.md.

Reporting Issues

Issues regarding the new API can be filed at github.com/golang/protobuf. Please use a APIv2: prefix in the title to make it clear that the issue is regarding the new API work.