[Swift-devel] a weekend playing with graphs

Ian Foster itf at mcs.anl.gov
Mon Sep 24 12:05:27 CDT 2007


We definitely need to be able to collect all the logs each time--we can't afford to repeat what seems to be a frequent situation where someone says "ah I forgot to get the falkonb log" or "I didn't have kickstart enabled"


Sent via BlackBerry from T-Mobile

-----Original Message-----
From: Ioan Raicu <iraicu at cs.uchicago.edu>

Date: Sun, 23 Sep 2007 13:56:07 
To:Ben Clifford <benc at hawaga.org.uk>
Cc:itf at mcs.anl.gov, swift-devel at ci.uchicago.edu
Subject: Re: [Swift-devel] a weekend playing with graphs


Ben Clifford wrote: On Sun, 23 Sep 2007, Ben Clifford wrote: those logs should be able to fit in with these too (i.e. another source of events to plot, sitting somewhere between the execute2 and kickstart layers) specifically this: GenericPortalWS_taskPerf.txt looks like it would fit in very well with what I'm working on are those urn: taskIDs coming from Swift? or are you making those yourself? Those are task IDs assigned by Swift!
 any new runs you do with falkon where submissions are being generated by swift, please keep a copy of the log and label it so that it can be correlated with the corresponding swift run logs. I save all the logs for important runs anyways... perhaps there should be some scripts that collect all the relevant logs (from Swift, Falkon, etc), label them accordingly, generate graphs, etc... all automatically when the workflow completes!
 
 Ioan
 
 -- ============================================ Ioan Raicu Ph.D. Student ============================================ Distributed Systems Laboratory Computer Science Department University of Chicago 1100 E. 58th Street, Ryerson Hall Chicago, IL 60637 ============================================ Email: iraicu at cs.uchicago.edu <mailto:iraicu at cs.uchicago.edu> Web: http://www.cs.uchicago.edu/~iraicu <http://www.cs.uchicago.edu/~iraicu> http://dsl.cs.uchicago.edu/ <http://dsl.cs.uchicago.edu/> ============================================ ============================================ 


More information about the Swift-devel mailing list