On Thu, 26 Oct 2006, Jonathan Myers wrote:
I ran some of my Python scripts on the logs, and I'm a little surprised to report that the "dry run" (without consumers) ran about 20 sec per image and the full run was 150 sec per image, bringing the total to ~ 130 sec per image. The main culprits are stage 3 and 4 (of 0 through 5 inclusive), which (when examined in NLV) look to be about 60 seconds each. Unfortunately, the policy directory is not publically readable, so I'm not positive what is causing the holdup.
I noticed this, too and am looking into it. In particular, I was looking at the contribution of stage 5. As you may know, we jacked up the filesize being written out for a test of the dbingest service. I think we can factor this out.
cheers, Ray _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
