Replying here on the mailing list thread.
>
Thanks AJ!>
> Using taskset is not an option for me, as my gRPC server is part of the executable that also does the more sensitive work IO load work. So what I need is an internal process differentiation between the threads' affinity. You wouldn't recommend patching the affinity into thd.cc because of the possible impact/side-effect on grpc behavior? or is there another reason I should be aware of??
Maintaining patches against gRPC may make it difficult to upgrade your library. It's best to stay up to date with the latest gRPC versions if possible, to take advantage of bug fixes, performance improvements, new features, etc.. You'll also be hard-pressed to get support for a modified library, presuming you run into something tricky and want to post here or to Stackoverflow. Those are my main reservations, but they're subjective, please do what makes sense for your use case.
>
> As for the EventEngine interface - this looks very interesting, I will take a look. Thanks. Where can I find the default gRPC implementation of the EventEngine?
>
> Thanks a lot,
> Dan