Background:
Machine: ~3.0Ghz, 8 cores (4 logical), 32.0 GB RAM
I was looking into grpc performance on large amounts of data to see if it
was viable for our use, data size could be over 10GB. The basic payload
would just be an array of floats. Using a synchronous server/client and
streams on
This is the discussion thread for the proposal at
https://github.com/grpc/proposal/pull/95
The proposal is to provide an option to set the socket TCP_USER_TIMEOUT for
platforms running on Linux kernels 2.6.37 and later.
--
You received this message because you are subscribed to the Google
Can you share your proto message definition?
On Wednesday, August 15, 2018 at 5:25:37 PM UTC-7, mken...@gmail.com wrote:
>
> Hello All, using python 3 the self.stub.filter_add() call below receives
> the following Traceback. It was my understanding the json.dumps() would
> correct this, but
I have a situation where I cancel a streaming RPC, upon which the client
will return grpc::CANCELLED on reader->Finish(). However it does this
directly because of the TryCancel on the client context, not because of the
controller return of the RPC.
Since my RPC using an exclusive resource,