Nicolas Cellier wrote:
> Concerning macro benchmark, StandardFileStream reading is already
> performant in case of pure Random access (upTo: is already buffered).
> The gain is for more sequence oriented algorithms. However, chances
> are that a loaded package has its source sequentially laid in changes,
> condenseChanges also organize source code that way, so Object
> compileAll might show a difference eventually.

Oh, it will. Here are the leaves for "Object compileAll":

**Leaves**
71.0 (1,149)  StandardFileStream  primRead:into:startingAt:count:
2.0 (32)  ByteString  at:put:
1.8 (29)  CompiledMethod  flushCache

That says that if you speed up #next by a factor of 5x (which is trivial 
using BufferedFileStream) it'll make compileAll 2-3x faster overall. I 
think we'll see similar 2x speedups for other common operations on 
source code (recent changes, browsing versions etc).

Faster I/O can make a *huge* difference in speed for the whole system.

Cheers,
   - Andreas