Mark DePristo bf81db40f7 NanoScheduler reducer optimizations ... -- reduceAsMuchAsPossible no longer blocks threads via synchronization, but instead uses an explicit lock to manage access. If the lock is already held (because some thread is doing reduce) then the thread attempting to reduce immediately exits the call and continues doing productive work. They removes one major source of blocking contention in the NanoScheduler		2012-12-24 13:35:57 -05:00
..
InputProducerUnitTest.java	Fundamentally better model for the NanoScheduler	2012-12-19 09:31:31 -05:00
MapResultUnitTest.java	MapResult compareTo() is now unit tested	2012-12-24 13:35:57 -05:00
NanoSchedulerIntegrationTest.java	Fix some of the broken integration tests	2012-10-26 11:23:44 -04:00
NanoSchedulerUnitTest.java	Minor optimizations for NanoScheduler	2012-12-24 13:35:56 -05:00
ReducerUnitTest.java	NanoScheduler reducer optimizations	2012-12-24 13:35:57 -05:00