It does matter in debug mode for stats collection and would affect epoll1 polling engine but other than that there is no effect currently. This function does NOT affect the number of threads being created.
On Thursday, May 30, 2019 at 12:44:35 AM UTC-7, wookieJ wrote: > > So You mean it doesn’t matter what this function returns, the results will > be the same? More threads would be created or something that could affect > application? I also wonder what would happen if our host returns large > number of cpu's even if we don't use them all, could it has negative > consequences. > > W dniu czwartek, 30 maja 2019 00:32:55 UTC+2 użytkownik Yash Tibrewal > napisał: >> >> gRPC uses that for some stats-keeping operations in debug mode, and it >> also seems to be used in epoll1 polling engine for determining the >> neighborhood (epollex is the default). Overall, you should not be worried >> about this. >> >> >> On Tuesday, May 28, 2019 at 5:10:05 AM UTC-7, wookieJ wrote: >>> >>> Hi everyone, I have problem with gRPC with lots of "Cannot handle >>> hot-plugged cpu" logs in stdout ( >>> https://github.com/grpc/grpc/blob/master/src/core/lib/gpr/cpu_linux.cc#L74). >>> >>> I want to ask you what returning value 0 in this function >>> "gpr_cpu_current_cpu()" affects in gRPC and what would happen if it starts >>> to return >0 value? >>> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/8fb4cc16-5251-4a8c-93f2-4dc8b37a4a65%40googlegroups.com.
