With Synchronous API, for integrators interested in having a little more control on the behavior of the thread pool (so for example, assigning the thread to the a particular core), they can define GRPC_CUSTOM_DEFAULT_THREAD_POOL and provide the implementation of the thread pool interface (which is literally just 1 function that adds work to the pool).
On Friday, March 3, 2017 at 7:57:27 AM UTC-8, Craig Tiller wrote: > > We don't have API's in place for the synchronous API, but for the async > API this is fairly easy (and indeed much of the point of that API) - you > get to call CompletionQueue::Next, and the thread that's calling that > function can be bound to a core. > > On Fri, Mar 3, 2017 at 7:40 AM <[email protected] <javascript:>> wrote: > >> Do you think this is possible? >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/30965964-0276-4327-9b1c-c141535cfef1%40googlegroups.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/860e0858-db55-4ed0-867c-c676068bd7d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
