[Swift-devel] CPU usage with provider-deef

[Ben Clifford]

ok.

So also Nika and Ioan had a problem where a workflow left running 
overnight ended up not completing - I think Falkon thinks it completed all 
of its job in a timely fashion, but that it seemed to take a (linearly 
increasing) amount of time for each job notification to be sent, and on 
the swift/provider-deef side of things, a large amount of CPU and not much 
else seemed to be happened.

That may or may not be related to the high CPU load below, but its 
probably worth investigating as it appears to break up large runs.

On Fri, 15 Jun 2007, Veronika Nefedova wrote:

> Ben,
> 
> we tested both my workflow and a simple "sleep" workflow. Both tests produced
> 100% CPU usage when ran with Falcon. When submitted directly to GRAM from
> swift - only a fraction of 1% CPU was used. I know that Yong did some
> additional testings, but I do not know the results.
> 
> Nika
> 
> On Jun 15, 2007, at 11:48 AM, Ben Clifford wrote:
> 
> > 
> > Yesterday, I was playing a bit with Ioan and Nika - they submitted a 68
> > node / 15 minute workflow through provider-deef & falkon and saw the swift
> > JVM on the submit node using about 100% CPU; then the same workflow
> > running through the GT2 GRAM provider rather than provider-deef and falkon
> > appeared to use significantly less.
> > 
> > I wandered off at that point so don't know if any interesting results came
> > after.
> > 
> > -- 
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > 
>