> On 9 Jun 2017, at 13:06, Holger Freyther <[email protected]> wrote:
>
> Hey!
>
> my current major deployment is still with Pharo3 and due some bigger changes
> I start to migrate to Pharo6 and today I finally managed to update the test
> deployment (and be happy with it). The test is not scientific but maybe an
> early indicator that there is something to look at?
>
> The image is idle and not handling any application payload so it might be a
> fair comparison because of that.
>
> RSS + ~16 MiB RAM (~53 Mib vs. ~69 Mib)
I think this is just size of image increase (e.g. new tools, tutorials,
demos...). We need to clean the image in Pharo7… e.g. remove
all the old versions of things that we have now a new version of.
For Pharo 6: you can unload some things (e.g. Help packages, maybe tests) to
shrink (see ImageCleaner).
For Pharo7 with the bootstrap we are already better: Image size is 30MB instead
of 36, and I think people will use
the bootstrap to build images specialised much more (e.g without UI, but remote
tools).
> CPU + ~0.005s per real second passed (think of Amazon AWS why that could
> matter)
> (In ~1400s wall clock 57.8s vs. 50.86s cpu time was used)
>
That is not good… I think there where some changes regarding the main rendering
loop. It might
be interesting to track them down (since Phaor3 that is a lot of potential
changes, though).
Or better, think about a better headless way of running servers (no UI, use
Remote tools instead).
Marcus
