On Tue, Sep 13, 2016 at 8:34 PM, <[email protected]> wrote: > I'm writing a rpc server/client very similar to the one on tutorial with > server-side pool connection. There are multiple clients and they requsted > at a defferent time. > > However, if the server receive an additional request while already > streaming to one client, these two requests always end simultaneously, and > the total transmiting time is longer than doing it seperately. So you can > imagine if I have 100 clients, the requests are never finished. > > I'm not sure if it is a config problem or other, has anyone run into > similar issues? >
It is unexpected that a server's servicing different, separate, unrelated RPCs will interfere with each other in this way. The first thing that comes to mind as a possibility is that you may have limited your server's thread pool to too few threads. What is the maximum number of threads you've set for your server-side thread pool? Even more information would be very helpful <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>. With what version of gRPC Python are you working, and on what platform and operating system? Are you able to share with us the code you've written that demonstrates the surprising behavior? Thanks much, -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/CAEOYnARW6LN6mrHzsh_OpUqMsc89cS6B9bSdZmEUCGW7O69%3DVQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
