2014-10-28 5:41 GMT-03:00 Sven Van Caekenberghe <sven@stfx.eu>:
Esteban,
The Reddit example's CI Job (https://ci.inria.fr/pharo-contribution/job/Reddit/) also loads Seaside and Glorp (two big packages) in Pharo 3 and it too results in a 110 Mb image and 142 Mb changes file. After condensing, that goes to 276 Mb !
I would say something is wrong here ;-)
Either something is wrong, or we feature it and rename PharoChangesCondenser>>#condense to PharoChangesExpander>>#expand :)
Note that condensing changes on newly loaded code should not make much difference (in essence, all multiple versions of methods are reduced to 1).
I think we should create some issues out of this.
This is true, however I find a changes of 140 megs to be MASSIVE. I remember loading ~4000 classes in the order of 10^6 LOC in Dolphin, and changes never got half that size. Sizes were ~28/55MB image/changes. The same in VAST, any image beyond the 20MB was an alert of something being leaked.
Hmm, we need more tests and data points, I will try on Linux command line later on.
I ran in it in Linux (Ubuntu) through the command line. Regards!