Ray (and others),
I tested on several images. I've tried it with the r. 556 stageleader
(only processes one image at a time) and the older version (several
images in the pipeline at once).
For future reference, the best latency time I've gotten is about 93
seconds per image, which is using the new stageleader (one image in the
pipeline at a time) and the new SetupHarnessPipeline.py (twice as many
MPI nodes as physical nodes, one stageslice per core). I tested got
about 12 images through before walltime shut me down.
Hope this clarifies things,
-Jon
Ray Plante wrote:
Hey Jon,
On Tue, 3 Oct 2006, Jonathan Myers wrote:
I've committed r.557 into subversion, which is a simple modification to
SetupHarnessPipeline.py. It lists every element of PBS_NODEFILE twice
in our nodelist, which actually doubles our MPI universe size and
doubles the number of stageslices on each node.
One more question so that I understand the results...Did you test just one
image or several? If it was the latter, did you have multiple images in
the pipeline at the same time?
Also, when you get a chance, could you explain a little more about how you
calculated flops for the different stages. If it's straight-forward, it
would be could to capture this as part of our regular statistics.
thanks!
Ray
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
