2016-11-14 16:24 GMT+01:00 Clément Bera <[email protected]>: > Hi Thierry, > > On the speed center you can compare 32 bits and 64 bits linux VMs: > http://squeak.org/codespeed/ > > Interesting to see the rsqueak results on that type of benchs. Mandelbrot would be the closest.
> > Normally Pharo 64 should be overall slightly slower than Pharo 32 because > 70% of the memory is used for pointers, implying twice more data to process > by the processor for pointer operations. Specific things, for example > SmallFloat arithmetic, should however be faster on 64 bits. > Yes, then it is a lot faster. > > For numerical code, benchs can be faster for two main reasons: > - the bench uses SmallFloat instead of BoxedFloat for most floats it uses > in 64 bits > - the bench overflows the 31bits signed integer range for SmallIntegers, > leading to the usage of LargeInteger in 32 bits, while it does not overflow > the 61 bits signed integer range in 64 bits. This is typically the case for > int32 benchs. > > Other numerical benchs may be faster on 32 bits. > > > On Mon, Nov 14, 2016 at 4:04 PM, Thierry Goubier < > [email protected]> wrote: > >> Has anybody seen performance differences between the 32bits and the >> 64bits versions of Pharo 6 ? >> >> I'm seeing a speedup greater than 2 on some intensive numerical code. >> >> Note that, on that code, Pharo 64bits is slower than R, by around 30%. >> The code overall is memory bound. >> >> Thierry >> >> >> > Thierry
