[Swift-devel] Clustering / wrapper.sh logging

Ben Clifford benc at hawaga.org.uk
Mon Oct 29 15:26:18 CDT 2007


so the wrapper.sh logging a put in suggests that everything encapsulated 
within wrapper.sh is not taking very long at all.

some scripted disgustingness gets me all the wrapper.sh start-end times 
for a particular cluster, and gives:

1193676034 -> 1193676037 RGI_Man_sh-o3ka5cji
1193676415 -> 1193676424 MassClass_sh_man-p3ka5cji
1193676645 -> 1193676649 MassClass_sh_man-q3ka5cji
1193676791 -> 1193676802 MassClass_sh_man-r3ka5cji
1193677076 -> 1193677088 RGI_Man_sh-t3ka5cji
1193677343 -> 1193677345 RGI_Man_sh-u3ka5cji
1193677616 -> 1193677620 RGI_Man_sh-s3ka5cji

There are large gaps (of hundreds of secodns) in the executions, when 
ideally the various wrapper.sh executions would butt up against each other 
closely.

I'm instrumenting seq.sh as mihael suggested. I'm also going to change its 
log handling so that it does not use a shared log file.

-- 



More information about the Swift-devel mailing list