This only applies to the cpp benchmarks. I am not very familiar with the
other language though, so they might have a similar architecture, but all
benchmarks are one language. We don't benchmark scenarios like a go client
talking to a cpp server yet.


On Tue, Mar 20, 2018 at 10:15 PM Thomas Ramfjord <[email protected]>
wrote:

> Would this just apply to the cpp benchmarks?  Or do all of the benchmarks
> communicate with a cpp server already? Thanks for all of the assistance
> you've already given.
>
>
>
> *From: *Noah Eisen <[email protected]>
> *Date: *Tuesday, March 20, 2018 at 7:40 AM
> *To: *Nan Dun <[email protected]>
> *Cc: *"grpc.io" <[email protected]>, Thomas Ramfjord <
> [email protected]>
> *Subject: *Re: [grpc-io] Multi-hop gRPC benchmark
>
>
>
> We do not have this functionality at the moment.
>
>
>
> We welcome external contributions if you would like to take a stab at it.
> I think you could use the proto, as is, and then add a new type of Worker
> called Proxy (currently a Worker can be either a Client or a Server). In
> the simplest case you would have three workers, and the test driver would
> tell one to become client, one to become server, and one to become proxy.
>
>
>
> All the code for that lives here:
> https://github.com/grpc/grpc/tree/master/test/cpp/qps
>
>
>
> On Tue, Mar 20, 2018 at 4:42 AM Nan Dun <[email protected]> wrote:
>
> Hi,
>
>
>
> Is there a simple way to run or extend gRPC performance benchmark (
> https://grpc.io/docs/guides/benchmarking.html) in a multi-hop way instead
> of current peer-to-peer ping pong? For example, we have three servers, A,
> B, C: A calls B, and then B calls C.
>
>
>
> Probably just extend the interface
> https://github.com/grpc/grpc/blob/master/src/proto/grpc/testing/services.proto
> to implement a service to relay the calls?
>
>
>
> Thanks!
>
> - Nan
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/grpc-io.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/55A41C99-16B4-4073-B4BE-2343E747FDB9%40quantcast.com
> <https://groups.google.com/d/msgid/grpc-io/55A41C99-16B4-4073-B4BE-2343E747FDB9%40quantcast.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAPYwnkiJ-2nMJJBBmCNTs%2BZCe98F0ExGkPpeE7rWNSRvA0YBDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to