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
..
net/sf	Cleanup of VCF header lines and constants, BCF2 bugfixes	2012-06-21 15:16:31 -04:00
org/broadinstitute	NanoScheduler reducer optimizations	2012-12-24 13:35:57 -05:00