Assuming we're talking about the C/C++ library, you're partially correct. Both the sync and callback API use multiple threads under the hood, created by gRPC. The Async CQ-based API requires the application to donate threads, so the thread count is controlled by you for the most part. For best performance, you'll likely want to donate <# of cpus> threads. See https://grpc.io/docs/guides/performance/
Best, -aj On Thursday, May 26, 2022 at 12:59:30 AM UTC-7 xied...@gmail.com wrote: > I have read tutorial and google for this question, but still have some > confuse? here is my understand about their difference. > 1. synchronous and callback grpc itself manage request and response queue > and thread model, but asynchronous let user provide a thread management, am > I right? > 2. sync and callback sytle is not multiple thread, am I right? > > thanks a very much > -- 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 grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/6c991b42-0db1-4476-90b6-774518454f9dn%40googlegroups.com.
