chibenwa commented on issue #167: URL: https://github.com/apache/apisix-java-plugin-runner/issues/167#issuecomment-2557169958
> Hmm, I may be wrong here. It's possible this will only block that specific connection's thread, in which case it's ok Yes by default Netty runs 2 x core event loops After being accepted each channel is assigned an event loop. But it's not like blocking a threadpool, channels are linked to an event loop. Unlike thread-pool tasks if blocked they wont be assigned another thread. This means blocking creates randomly non local delays onto completly unrelated channels, and have disastrous performance impact. Blocking on an event loop should be avoided at all cost. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
