Nick Hill feb804dca8 Avoid extra Runnable allocs when scheduling tasks outside event loop (#9744) ... Motivation Currently when future tasks are scheduled via EventExecutors from a different thread, at least two allocations are performed - the ScheduledFutureTask wrapping the to-be-run task, and a Runnable wrapping the action to add to the scheduled task priority queue. The latter can be avoided by incorporating this logic into the former. Modification - When scheduling or cancelling a future task from outside the event loop, enqueue the task itself rather than wrapping in a Runnable - Have ScheduledFutureTask#run first verify the task's deadline has passed and if not add or remove it from the scheduledTaskQueue depending on its cancellation state - Add new outside-event-loop benchmarks to ScheduleFutureTaskBenchmark Result Fewer allocations when scheduling/cancelling future tasks		2019-11-04 11:57:53 +01:00
..
src	Avoid extra Runnable allocs when scheduling tasks outside event loop (#9744)	2019-11-04 11:57:53 +01:00
pom.xml	Add BlockHound integration that detects blocking calls in event loops (#9687)	2019-10-25 06:14:14 -07:00