He-Pin opened a new issue, #3254: URL: https://github.com/apache/pekko/issues/3254
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. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
