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)
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)
Does anyone else see this increased usage? Has anyone explored the source of
it? Does anyone of you share the concern I have? :)
holger
Outline of the setup:
* Take a Pharo3 or Pharo6 base image
* Load my code (and its dependencies, big difference is version of Voyage)
* Start the images on the test system
* Opens a TCP connection, initialize VoyageMongo
* Wait for work
Look at top for RSS and CPU time used.
