Carl Mastrangelo f01278616a Properly debounce wakeups (#9191) ... Motivation: The wakeup logic in EpollEventLoop is overly complex Modification: * Simplify the race to wakeup the loop * Dont let the event loop wake up itself (it's already awake!) * Make event loop check if there are any more tasks after preparing to sleep. There is small window where the non-eventloop writers can issue eventfd writes here, but that is okay. Result: Cleaner wakeup logic. Benchmarks: ``` BEFORE Benchmark Mode Cnt Score Error Units EpollSocketChannelBenchmark.executeMulti thrpt 20 408381.411 ± 2857.498 ops/s EpollSocketChannelBenchmark.executeSingle thrpt 20 157022.360 ± 1240.573 ops/s EpollSocketChannelBenchmark.pingPong thrpt 20 60571.704 ± 331.125 ops/s Benchmark Mode Cnt Score Error Units EpollSocketChannelBenchmark.executeMulti thrpt 20 440546.953 ± 1652.823 ops/s EpollSocketChannelBenchmark.executeSingle thrpt 20 168114.751 ± 1176.609 ops/s EpollSocketChannelBenchmark.pingPong thrpt 20 61231.878 ± 520.108 ops/s ```		2019-06-04 05:27:15 -07:00
..
buffer	The benchmark is not taking into account nanoTime granularity (#9033)	2019-04-15 15:15:08 +02:00
handler/codec	Merge ChannelInboundHandler and ChannelOutboundHandler into ChannelHa… (#8957)	2019-03-28 09:28:27 +00:00
microbench	Properly debounce wakeups (#9191)	2019-06-04 05:27:15 -07:00
microbenchmark/common	Java 8 migration: Use diamond operator (#8749)	2019-01-22 16:07:26 +01:00