In Cats Effect, IO and the scheduler are tightly integrated; similarly, the new Netty architecture supports various IOHandler and IOHandle implementations within the EventLoop, leveraging abstractions to enhance CPU reuse and reduce latency. Explorations such as https://github.com/franz1981/Netty-VirtualThread-Scheduler are also worth studying. Currently, Pekko’s default implementation relies on ForkJoinPool, and the latest version of ForkJoinPool now implements ScheduledExecutorService, thereby supporting time-based scheduling. I believe we should examine all these approaches—for instance, Netty’s EventLoop already supports time-based scheduling. Within Pekko, AffinityPool seems like the most suitable place to explore these practices.
In Cats Effect, IO and the scheduler are tightly integrated; similarly, the new Netty architecture supports various
IOHandlerandIOHandleimplementations within theEventLoop, leveraging abstractions to enhance CPU reuse and reduce latency. Explorations such as https://github.com/franz1981/Netty-VirtualThread-Scheduler are also worth studying. Currently, Pekko’s default implementation relies onForkJoinPool, and the latest version ofForkJoinPoolnow implementsScheduledExecutorService, thereby supporting time-based scheduling. I believe we should examine all these approaches—for instance, Netty’sEventLoopalready supports time-based scheduling. Within Pekko,AffinityPoolseems like the most suitable place to explore these practices.