gatk-3.8/public/java/test/org/broadinstitute/sting/utils/nanoScheduler
Mark DePristo 0f04485c24 NanoScheduler optimization: don't use a PriorityBlockingQueue for the MapResultsQueue
-- Created a separate, limited interface MapResultsQueue object that previously was set to the PriorityBlockingQueue.
-- The MapResultsQueue is now backed by a synchronized ExpandingArrayList, since job ids are integers incrementing from 0 to N.  This means we avoid the n log n sort in the priority queue which was generating a lot of cost in the reduce step
-- Had to update ReducerUnitTest because the test itself was brittle, and broken when I changed the underlying code.
-- A few bits of minor code cleanup through the system (removing unused constructors, local variables, etc)
-- ExpandingArrayList called ensureCapacity so that we increase the size of the arraylist once to accommodate the upcoming size needs
2012-12-24 13:35:56 -05:00
..
InputProducerUnitTest.java Fundamentally better model for the NanoScheduler 2012-12-19 09:31:31 -05:00
NanoSchedulerIntegrationTest.java Fix some of the broken integration tests 2012-10-26 11:23:44 -04:00
NanoSchedulerUnitTest.java Major performance improvement to the GATK engine 2012-12-05 14:49:22 -05:00
ReducerUnitTest.java NanoScheduler optimization: don't use a PriorityBlockingQueue for the MapResultsQueue 2012-12-24 13:35:56 -05:00