problem with shared heap?

[Matthias Lang]

david wallin writes:

 > Yes, but when shared heap is finished, will there be cases when running
 > a shared heap will actually perform worse than without it, or is it just
 > now in its experimental stages that these things can occur?

Why would you expect the shared heap to be faster in _all_ cases?

Related observations:

  * Native code is not necessarily faster than BEAM.

  * Binaries are not always faster than lists.

  * Tail recursive algorithms are not always faster than non-tail 
    recursive ones.

Matthias