How did you identify that these threads are a bottleneck for your application? If your application is idle, the event_engine threads will be waiting for work (via condvar wait, which will not tie up your CPU). If on the other hand there's work to be done, those threads will wake up and do that work. The existence of idle/waiting threads should not cause any decrease in performance, and otherwise all active threads are doing their jobs.
If you are using the C++ callback API, then note that your callbacks may run on these `event_engine` threads, so any blocking behavior seen here may also be your own. On Tuesday, October 1, 2024 at 1:44:12 PM UTC-7 Amirsaman Memaripour wrote: > Hi folks, > > I'm facing scalability issues when using the C++ CQ-based server with TLS. > In particular, the `event_engine` thread is fully utilizing its core, > making it the bottleneck and limiting server's throughput. I was wondering > if there is an option to change the number of threads assigned to the > `event_engine`? > > [image: screenshot.png] > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/0fe94064-61b5-48e4-a58d-627a92c2c151n%40googlegroups.com.
