I'm very happy to see that the 64 bit Pharo vm is progressing.

I've even managed to get a ~6.85 GB heap allocated (see��http://bit.ly/2lbp8n6).

This is great!

There seems however to be a small problem with the #shallowCopy message, which is 2.63 times slower on the 64bit VM (image/vm details bellow).

The bench that I used is a simple random graph analysis tool that is intended to do a lot of random memory accesses on big heaps, which is accessible at��http://www.smalltalkhub.com/#!/~CipT/PlugMC

In this case I expect the execution time to be dominated by the Set implementation (which is the case with pharo 5 -- see��http://bit.ly/2lbzJhd), and not by the array copy (see http://bit.ly/2kvbqvy).