|
|
|
@ -16,7 +16,7 @@ build your language's protobuf, then: |
|
|
|
|
You need to install [cmake](https://cmake.org/) before building the benchmark. |
|
|
|
|
|
|
|
|
|
We are using [google/benchmark](https://github.com/google/benchmark) as the |
|
|
|
|
benchmark tool for testing cpp. This will be automaticly made during build the |
|
|
|
|
benchmark tool for testing cpp. This will be automatically made during build the |
|
|
|
|
cpp benchmark. |
|
|
|
|
|
|
|
|
|
The cpp protobuf performance can be improved by linking with [tcmalloc library]( |
|
|
|
@ -28,7 +28,7 @@ libtcmallc.so library. |
|
|
|
|
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. |
|
|
|
|
can be automatically included by maven. |
|
|
|
|
|
|
|
|
|
### Python |
|
|
|
|
We're using python C++ API for testing the generated |
|
|
|
@ -59,7 +59,7 @@ The first command installs `protoc-gen-go` into the `bin` directory in your loca |
|
|
|
|
The second command adds the `bin` directory to your `PATH` so that `protoc` can locate the plugin later. |
|
|
|
|
|
|
|
|
|
### PHP |
|
|
|
|
PHP benchmark's requirement is the same as PHP protobuf's requirements. The benchmark will automaticly |
|
|
|
|
PHP benchmark's requirement is the same as PHP protobuf's requirements. The benchmark will automatically |
|
|
|
|
include PHP protobuf's src and build the c extension if required. |
|
|
|
|
|
|
|
|
|
### Node.js |
|
|
|
|