franz1981/Netty-VirtualThread-Scheduler

AI Summary: The task requires investigating and potentially modifying the Netty VirtualThread Scheduler to use a single scheduler instance instead of one per event loop. This involves exploring the implications for work-stealing and poller locality, potentially requiring API changes to leverage the benefits of a single scheduler instance while maintaining or improving performance, especially concerning the latency of waking blocked reads. Benchmarking will be crucial to validate any changes.