2010/8/24 Sven Van Caekenberghe <sven@beta9.be>

Well, my 1.1 dev image has:

Class � � � � � � � � � � � � � code space # instances �inst space percent
Bitmap � � � � � � � � � � � � � � � �3753 � � � �8906 � � �19427212 � �31.9
ByteString � � � � � � � � � � � � � �2515 � � �190202 � � �17459895 � �28.6
Array � � � � � � � � � � � � � � � � 2176 � � �137567 � � � 5198744 � � 8.5
CompiledMethod � � � � � � � � � � � 19130 � � � 79223 � � � 4888481 � � 8.0
ByteSymbol � � � � � � � � � � � � � �1062 � � � 52650 � � � 1330679 � � 2.2
MethodDictionary � � � � � � � � � � �2135 � � � �9854 � � � 1302376 � � 2.1
MCVersionInfo � � � � � � � � � � � � 1313 � � � 22841 � � � �913640 � � 1.5
Association � � � � � � � � � � � � � �710 � � � 74216 � � � �890592 � � 1.5
Character � � � � � � � � � � � � � � 6355 � � � 66219 � � � �794628 � � 1.3
DateAndTime � � � � � � � � � � � � � 7893 � � � 28026 � � � �672624 � � 1.1
ByteArray � � � � � � � � � � � � � � 3458 � � � � 640 � � � �639048 � � 1.0

While my 1.1. deploy image (incl Seaside 3 and Glorp) has:

CompiledMethod � � � � � � � � � � � 18784 � � � 53888 � � � 3082849 � �20.7
Bitmap � � � � � � � � � � � � � � � �3753 � � � � 184 � � � 2837256 � �19.0
ByteString � � � � � � � � � � � � � �2515 � � � 47865 � � � 2713211 � �18.2
Array � � � � � � � � � � � � � � � � 2176 � � � 45399 � � � 2277268 � �15.3
ByteSymbol � � � � � � � � � � � � � �1062 � � � 37522 � � � �925078 � � 6.2
Character � � � � � � � � � � � � � � 6355 � � � 66219 � � � �794628 � � 5.3
MethodDictionary � � � � � � � � � � �2135 � � � �6296 � � � �468456 � � 3.1
WeakArray � � � � � � � � � � � � � � �718 � � � � 127 � � � �324104 � � 2.2
Association � � � � � � � � � � � � � �710 � � � 23189 � � � �278268 � � 1.9
ByteArray � � � � � � � � � � � � � � 3370 � � � � 341 � � � �213357 � � 1.4
ClassOrganizer � � � � � � � � � � � �1326 � � � �6112 � � � �195584 � � 1.3
Metaclass � � � � � � � � � � � � � � 3909 � � � �3078 � � � �123120 � � 0.8

This reduction is done by ScriptLoader>>#cleanUpForRelease (after deleting all unit test packages).

Thanks Sven. It seems my mail was not clear at all. I know that with #cleanUpForRelease it will reduce, but my question is....if I understand correlty what a Bitmap is, why they are nstantiated when I am running headless?� shouldn't the amount of instances be 0?

I think I don't understand what really the -headless does. I thought the world was not display, not Bitmap was instanciated, etc...

cheers

Mariano

�

HTH,

Sven

On 24 Aug 2010, at 14:18, Mariano Martinez Peck wrote:

I took a dev image, and run them in two ways: the normal and headless. For each I did a:

"Smalltalk garbageCollect.
SpaceTally new printSpaceAnalysis"

Normal one:

Class�� code space # instances� inst space percent
Bitmap�� 3753�� 133�� 11099904�� 37.4
ByteString�� 2515�� 85110�� 6106378�� 20.6
CompiledMethod�� 19130�� 59452�� 3703463�� 12.5
Array�� 2176�� 77579�� 2561928�� 8.6
......

Headless:

Class�� code space # instances� inst space percent
ByteString�� 2515�� 85110�� 6106378�� 24.7
Bitmap�� 3753�� 126�� 6049208�� 24.5
CompiledMethod�� 19130�� 59452�� 3703463�� 15.0
Array�� 2176�� 77577�� 2561844�� 10.4
......

So....even in headless mode, I have 133 instances of Bitmap, representing 24.5% of the memory.... Ok, 24.5 is better than 37.5, but I don't understand why Bitmap instances are created. Why they are needed ? is there a way to garbageCollect them?

thanks

Mariano
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project