Norman Maurer 2f7d60f234 Minimize memory footprint of HashedWheelTimer and context-switching ... Motivation: At the moment there are two issues with HashedWheelTimer: * the memory footprint of it is pretty heavy (250kb fon an empty instance) * the way how added Timeouts are handled is inefficient in terms of how locks etc are used and so a lot of context-switching / condition can happen. Modification: Rewrite HashedWheelTimer to use an optimized bucket implementation to store the submitted Timeouts and a MPSC queue to handover the timeouts. So volatile writes are reduced to a minimum and also the memory foot-print of the buckets itself is reduced a lot as the bucket uses a double-linked-list. Beside this we use Atomic*FieldUpdater where-ever possible to improve the memory foot-print and performance. Result: Lower memory-footprint and better performance		2014-05-11 15:12:29 +02:00
..
java/io/netty/util	Minimize memory footprint of HashedWheelTimer and context-switching	2014-05-11 15:12:29 +02:00