[Swift-devel] more on job throughput

[wilde at mcs.anl.gov]

Is this test run telling us:

- overall, 8192 jobs in 25 seconds: 328 jobs / sec

- about 5 seconds for anything to start, so:
  8192 jobs / 20 seconds: 409 jobs / sec

- drop off site select time (can bypass for single-site case?) and
  stage in (can bypass w/CDM?) and we are at the number you mentioned
  in an earlier thread: 8192 jobs / 10 seconds = 819 jobs / sec ?

Seems a major question is what is practical with a real providers, eg coasters on BG/P?  And can the 15 seconds of "overhead" (out of 25 sec) in this run be eliminated or reduced?

- Mike



----- "Mihael Hategan" <hategan at mcs.anl.gov> wrote:

> Here's a plot of the number of tasks in the various stages that the
> runtime stats track.
> 
> This is with 8192 jobs and the fake provider (which does nothing and
> finishes tasks almost immediately, and which I should probably commit
> somewhere if anybody else wants to play with this).
> 
> I also attached the scripts used. You would need to change
> RuntimeStats
> to print the stats more often than the 1s default (say something like
> (MIN,MAX)_PERIOD_MS=100).
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory