Sorry for hijacking into this thread, I ran into some weird SIGSEGV with
c++ async server, I think I may have hit some internal grpc bugs and am
wondering if AsyncNotifyWhenDone will be the cure.
I have a pretty vanilla c++ async server, closely following the hello world
example, my question
t; server. There is no way to configure the max number of threads either. It
> is really imo a sloppy design. threads aren’t free and this framework keeps
> (in my case) dozens and dozens of idle threads around even during long
> periods of low or no traffic. Maybe they fixed it in newer ver
Hi Jeff and Mark,
I just ran into the same issue with an async c++ GRPC server (version
1.37.1), was curious about these default-executo threads and then got this
thread, did you guys figure out what these threads are for? The number
seems to be about 2x of the polling worker threads.
Thanks!
