Netty currently only provides a priority queue based task scheduler. We could add a small abstraction layer between EventExecutor and a task scheduler implementation so that a user can choose his or her favorite scheduler algorithm, most notably, hashed wheel timer, which is more scalable.

(Inspired by an e-mail question by Mac Atre.)