[Swift-devel] Re: Drop kickstart, adopt wrapper logs?

[Mihael Hategan]

In the really long run if coasters turn out to be a workable piece of
software, they could support remote logging, which would mean streaming
logging data instead of using the filesystem.

But for the short term, I agree. We haven't exercised kickstart as much,
and the wrapper logs seem to be reasonably useful as a replacement.

On Fri, 2008-07-25 at 15:15 +0000, Ben Clifford wrote:
> pretty much no one uses kickstart with swift at the moment. The wrapper 
> log *is* in a useful format, and is probably as specified as any other 
> part of the runtime environment.
> 
> 
> > was: Re: Can we copy Swift execution logs to CI network?
> > 
> > Should we make this transition, dropping kickstart, and making the wrapper log
> > a useful format that becomes part of the Swift runtime specification?
> > 
> > On 7/15/08 4:18 PM, Ben Clifford wrote:
> > <snip>
> > > ...there's substantial lack of information
> > > for many runs as we have been tweaking the logs over time (especially the
> > > worker node logs which take a similar place to kickstart records now -
> > > giving the actual on-worker cpu usage but are relatively very expensive to
> > > collect and move around).
> > 
> > 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel