[Fwd: Re: [Swift-devel] Re: swift-falkon problem... plots to explain plateaus...]

[Mihael Hategan]

> > >     
> > 
> > Doing nothing can be incredibly fast.
> >   
> What I meant is that we need to move these operations to the local
> file system, i.e. RAM.  We have run applications on BG/P via Falkon
> only, and implemented a caching strategy that caches all scripts,
> binaries, and input data, to RAM... once the task execution (all from
> RAM) completes, and has written its output to RAM, then there is a
> single copy operation of the output data from RAM to GPFS.  We control
> how frequently this copy operation occurs, so we can essentially scale
> quite nicely and linearly with this approach.  The hope is that we can
> eventually work this kind of functionality in the wrapper.sh, or in
> Swift itself.  So, a reply to your statement, we would like to
> preserve the functionality of the wrapper.sh, but move as much as
> possible of that functionality from a shared file system to a local
> disk. 
> 

Having optimized wrappers for different architectures is a perfectly
valid option.

Mihael