Re: [grpc-io] Thread configuration for low latency in high throughput scenario

2018-11-29 Thread 'Carl Mastrangelo' via grpc.io
+1 To what Robert said. You have a couple options here: * use ForkJoinPool, which scales much more gracefully under load. * If your RPC logic is pretty simple, and does not block (like, ever), you can use directExecutor() on the server builder and run RPCs inline. This avoids the need

Re: [grpc-io] Thread configuration for low latency in high throughput scenario

2018-11-27 Thread robert engels
If you get multiple requests that are external, and all of these take 200ms, you are going to be blocked… if the requests are IO bound, then 4 is too small for the pool, and by increasing the pool size if other requests arrive that are not external they can be handled > On Nov 27, 2018, at