On Fri, Nov 17, 2017 at 12:28 PM, Jessica <[email protected]> wrote:
> Does the same threading model apply across all supported gRPC supported > languages (i.e. Python)? > No. gRPC's threading models are generally per-language and customized to the available libraries and advised best practices of the particular programming language. [...] > > Can anyone expound upon the threading model for Python? > The current service-side threading model for gRPC Python is that the application passes at Server construction time a thread pool in which the application's RPC service behaviors will be called <https://grpc.io/grpc/python/grpc.html#grpc.server>. We've had some users hit some scaling problems with this, particularly in the case of long-lived RPCs that exhaust the pool's threads and prevent service of any other RPCs. We have a few ideas <https://github.com/grpc/grpc/issues/7632> for how to improve the design <https://github.com/grpc/grpc/issues/5762> but nothing in place and supported at this time. -Nathaniel -- 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/CAEOYnATrnDO%2BAGDYQHd65MVOC42qMsVH%3DrnqnNvdNGq1HLpUcg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
