[Swift-devel] Coaster capabilities for release 0.9

[Michael Wilde]

was: Re: [Swift-devel] coaster block allocations

I have not been able to try this yet - been working on grant deadlines.

But regarding an "idea of how things (will) work" - please send an 
update on the coaster development - are you proceeding with the 3-level 
allocation strategy you outlined in a prior thread, and how is that 
progressing?

What is on the list of priority fixes or enhancements to coasters?

Which of these can make it into 0.9? (I would like see 0.9 have a highly 
usable coaster release with a converging set of capabilities. I would 
argue to delay 0.9 by up to 2 weeks to get it in, if needed enhancements 
are close)

I agree with Ben that coaster testing (and implicitly coaster stability) 
  is important for this release; I would like to see us push to get the 
feature into a state where its broadly usable and heavily used.


On 4/17/09 4:33 PM, Mihael Hategan wrote:
> I mentioned a simulator:
> http://www.mcs.anl.gov/~hategan/CS.java
> 
> It will given you a visual idea of how things (will) work (run it and
> press the up key to advance time). You can play with parameters, work
> loads and pre-allocations.
> 
> If you find some behavior that you don't like, send me the parameters
> (which are printed when you close the window) and work load (which
> you'll have to manually paste from the code), so that I can reproduce
> it.
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel