Hi Louis,
In order to simplify the case I tested very simple message.
The proto file looks like:
rpc SimpleMessage(SimpleByteArray) returns (Empty) {}
message Empty {
}
message SimpleByteArray {
bytes byte_array = 1;
}
Again I made iterations of growing message size from 500 bytes to 35KB and
again around 9K the call time started to jump to around 220ms.
I also noticed that also in the large messages sometime the call time drop
again to around 20ms.
The graph looks like:
[cid:[email protected]]
The serialization and deserialization time seems negligible, even for large
message (1MB) the serialization time is 2ms and the deserialization is less
than 1ms.
I measured the serialization by measuring the function
SerializationTraits<M>::Serialize(message, &send_buf_, &own_buf_); in call.h;
and the deserialization by measuring the function
SerializationTraits<RequestType>::Deserialize(param.request, &req,
param.max_message_size); in method_handler_impl.h
I will appreciate if you can give me more sampling places in the code in order
to profile the gRPC and understand better this issue.
Thanks,
Meir
From: Louis Ryan [mailto:[email protected]]
Sent: Thursday, July 28, 2016 3:31 AM
To: Meir Vengrover
Cc: grpc-io
Subject: Re: [grpc-io] gRPC call time overhead
A step function like that is pretty odd. What kind of payload are you using?
Just to isolate that out could you benchmark your message serialization for the
same range of sizes?
As a general rule I would expect to see a benchmark of sequential
request/responses with 'typical' 1k protobufs between two normal servers on the
same LAN to be sub-ms.
On Wed, Jul 27, 2016 at 7:11 AM,
<[email protected]<mailto:[email protected]>> wrote:
Hello gRPC group,
I’m working in Applied Materials SW team, and we’re checking the possibility of
replacing our RPC based CORBA with gRPC.
My benchmark includes comparing gRPC vs CORBA performance while sending
various message sizes from client to server.
The server replays immediately for each call.
Both client and server are C++ based, and I’m using windows.
I noticed that for small messages one RPC time is about ~20 ms between the two
computers (from the client call until it gets response).
But from a certain message size the call time jump to ~220 ms.
I see this 200ms overhead from above ~9500 bytes during connection, and with
message size over ~1070 when I just start connection.
When performing many gRPC calls this 200ms overhead become a problem.
Please see the following graph which represents call time vs message byte size.
[cid:[email protected]]
When using CORBA (which is also based TPC) I don’t see such overhead, a call
takes ~15ms.
Are you familiar with such behavior?
Can you explain it?
Thanks
Meir Vengrover,
SW engineer, Applied Materials.
--
You received this message because you are subscribed to the Google Groups
"grpc.io<http://grpc.io>" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
[email protected]<mailto:[email protected]>.
To post to this group, send email to
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/EA173EF8BDC63545970E3E597732992F81893F%40045-SN2MPN4-071.045d.mgd.msft.net<https://groups.google.com/d/msgid/grpc-io/EA173EF8BDC63545970E3E597732992F81893F%40045-SN2MPN4-071.045d.mgd.msft.net?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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/EA173EF8BDC63545970E3E597732992F818B7E%40045-SN2MPN4-071.045d.mgd.msft.net.
For more options, visit https://groups.google.com/d/optout.
