gRPC Server Core Affinity

[shak...@gmail.com]

Hi, my understanding is once started the server maintains a pool of threads which it dispatches work to as a connection is established. Is there any way to specify the core affinity to these threads if we don't want them floating?

[Carl Mastrangelo]

What language?

[Cliff Burdick]

C++

[shak...@gmail.com]

Do you think this is possible?

[Craig Tiller]

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 <shak...@gmail.com> 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 grpc-io+u...@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
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.

[Cliff Burdick]

Thanks for the answer

On Fri, Mar 3, 2017 at 7:57 AM, Craig Tiller <cti...@google.com> 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 <shak...@gmail.com> 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 grpc-io+unsubscribe@googlegroups.com.

[Arpit Baldeva]

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).