> | No other scheduler we have used > | comes close to this kind of performance. Scheduler overhead was > | basically insignificant. > > Probably apples and oranges, but Jim Kent wrote a job scheduler for his > kilocluster that nicely handled about 1M jobs in six hours. It's the > standard thing for whole genome sequence alignments at ucsc.
the vitanuova guys probably have better numbers, but when we ran their grid code at ucalgary it executed over a million jobs in a 24-hour period. the jobs were non-null (md5sum using inferno's dis code). it ran on a 12 (or so) -node cluster :)
