Add a section about gRPC performance and link to gRPC performance dashboard (once ready) about grpc.github.io HOT 18 CLOSED

CC @hsaliak

from grpc.github.io.

Would we have this as a separate doc in the Guides or Reference section, do you think?

from grpc.github.io.

Yes, I think it should be in the Guides section. What it should contain (just a braindump of some of my thoughts).

1. Some statement about what we are trying to achieve (that gRPC is supposed to be high-performance, low-overhead and should work well under heavy-load situation). We might also mentions that google is planning to use gRPC internally to run its production services.
2. A paragraph about how we measure, link to performance dashboard, link to a performance REAME.md (doesn't exist yet).

from grpc.github.io.

CC @vjpai

from grpc.github.io.

OK, do you want to try to put together some rough information and then I can turn it into something nice and shiny for the site?

from grpc.github.io.

@vjpai can you try to put together some basic info?

from grpc.github.io.

@vjpai we need performance numbers for the existing v1.0.x branch, so that users see the performance characteristics for the stable release. Given that it may see lesser commits than master, an alternative representation such as a table of benchmarks with %tile numbers may be sufficient.
/cc @jayantkolhe
I believe that @adelez is working on this?

from grpc.github.io.

Yes, I'm working with sreek@ on this. Already uploaded data for 32core
tests but seeing failures for 8core. Investigating.

On Tue, Aug 2, 2016 at 10:50 AM, Kailash Sethuraman <
[email protected]> wrote:

@vjpai https://github.com/vjpai we need performance numbers for the
existing v1.0.x branch, so that users see the performance characteristics
for the stable release. Given that it may see lesser commits than master,
an alternative representation such as a table of benchmarks with %tile
numbers may be sufficient.
/cc @jayantkolhe https://github.com/jayantkolhe
I believe that @adelez https://github.com/adelez is working on this?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#179 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOPYhFGhDOokCGSR90QT64uzl2-zwzxhks5qb4NugaJpZM4IOBYV
.

from grpc.github.io.

/cc @sreecha

from grpc.github.io.

Here is the dashboard:
https://performance-dot-grpc-testing.appspot.com/explore?dashboard=5738600293466112&widget=952298825&container=846542667

On Tue, Aug 2, 2016 at 10:57 AM, Kailash Sethuraman <
[email protected]> wrote:

/cc @sreecha https://github.com/sreecha

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#179 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOPYhJY1CuohC33CG6OoZOOZtbDTCabbks5qb4UdgaJpZM4IOBYV
.

from grpc.github.io.

Thanks @adelez can we represent the data in any other format (Eg: a table) given that we may not get pull requests that often into the 1.0 branch?
Also @vjpai would you be providing a short write up that accompanies?

from grpc.github.io.

Recreated the GA dashboard at
https://performance-dot-grpc-testing.appspot.com/explore?dashboard=5712453606309888&widget=1747498211&container=897341821

However, Go is still built from the master branch. What's the way to get
the GA build for Go?
The following Python tests are not in the database for some reason, most
like they failed:
python_protobuf_sync_unary_ping_pong
python_to_cpp_protobuf_sync_unary_ping_pong
python_protobuf_sync_streaming_ping_pong

On Tue, Aug 2, 2016 at 3:45 PM, Kailash Sethuraman <[email protected]

wrote:

Thanks @adelez https://github.com/adelez can we represent the data in
any other format (Eg: a table) given that we may not get pull requests that
often into the 1.0 branch?
Also @vjpai https://github.com/vjpai would you be providing a short
write up that accompanies?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#179 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOPYhGS222AeitznC0ZCMJFLHk1Fr8fDks5qb8imgaJpZM4IOBYV
.

from grpc.github.io.

@vjpai Ping on this issue -- could you please help with this section?

from grpc.github.io.

@adelez for Go, we will mainly be tracking master and will only have a release tag, so a dynamic performance dashboard on 1.0 is not meaningful there.
@nathanielmanistaatgoogle can you comment on the failed tests?

@vjpai ETA on the performance section?

from grpc.github.io.

On Tue, Aug 16, 2016 at 4:24 PM, Kailash Sethuraman <
[email protected]> wrote:

@adelez https://github.com/adelez for Go, we will mainly be tracking
master and will only have a release tag, so a dynamic performance dashboard
on 1.0 is not meaningful there.

I'll remove Go from the GA perf test and dashboard.

@nathanielmanistaatgoogle https://github.com/nathanielmanistaatgoogle
can you comment on the failed tests?

@vjpai https://github.com/vjpai ETA on the performance section?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#179 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOPYhCsQwwVNAddwh6EB_d_wYVn265Buks5qgkbAgaJpZM4IOBYV
.

from grpc.github.io.

@hsaliak: not without more information. @adelez: do you have logs or output or anything else from the Python tests?

from grpc.github.io.

The python tests are passing now.

On Tue, Aug 16, 2016 at 5:32 PM, Nathaniel Manista <[email protected]

wrote:

@hsaliak https://github.com/hsaliak: not without more information.
@adelez https://github.com/adelez: do you have logs or output or
anything else from the Python tests?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#179 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOPYhPfYJYqEHF8IjXIepJ1NTFKbl45nks5qglaTgaJpZM4IOBYV
.

from grpc.github.io.

Fixed by #331

from grpc.github.io.