September 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Image size

by Marcus Denker

On 19.09.2008, at 10:42, StÃ©phane Ducasse wrote: > did you flush the changesets ? That's important. Adrian lienhard sent this around some time ago some cleanup code. Here is an updated version: ScriptLoader new cleaningCS. RequiredSelectors initialize. ProvidedSelectors initialize. LocalSends initialize. Utilities cleanseOtherworldlySteppers. Smalltalk organization removeEmptyCategories. SystemBrowser removeObsolete. TheWorldMenu removeObsolete. AppRegistry removeObsolete. MCFileBasedRepository flushAllCaches. MCDefinition clearInstances. Symbol compactSymbolTable. Set rehashAllSets. Smalltalk cleanOutUndeclared. Smalltalk garbageCollect. --> 13.7 MB 3.9 was 15.6 MB There is more code for cleaning in the "cleaning" category of ScriptLoader. #initialCleanup and #finalCleanup. (we should merge the code above in the cleanup methods) The changesets are the majority of the space, another 100K or so comes from rehashing the sets. This is I think because the methodDictionaries are degenerating very fast when adding / replacing methods. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Sept. 19, 2008

Re: [Pharo-project] CS in pharo

by Lukas Renggli

FYI, there is a working infrastructure for atomic loading here: http://source.wiresong.ca/mc/SystemEditor-mtf.69.mcz Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 19, 2008

Re: [Pharo-project] Image size

by Norbert Hartl

On Fri, 2008-09-19 at 10:42 +0200, StÃ©phane Ducasse wrote: > did you flush the changesets ? > because it keeps a reference also to any changes. > Ah, learned something new :) That freed more than 1 megabyte. So it is 5% smaller than squeak. Any other hints? :) thanks, Norbert > Stef > > On Sep 19, 2008, at 10:36 AM, Norbert Hartl wrote: > > > Hi, > > > > I have problems in understanding the image size of pharo. > > I monitored it since we started and I did not recognize > > a notably change. So I took a pharo 10073 and squeak 3.10.2 > > for comparsion. > > yes frustrating after removing MVC and more. > > > > Amount classes, amount methods and lines of code are all 10% > > less in pharo. But the image is approx. 0,5% - 1% smaller > > than the squeak one. > > > > To clarify this. I closed all windows and did condenseChanges > > and garbageCollect, flushed the monticello cache... > > > > What could be the reason for this? > > > > thanks, > > > > Norbert > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 19, 2008

Re: [Pharo-project] 10073 error

by StÃ©phane Ducasse

Indeed now I get the complete recompilation working. > May be got an hiccup bvecause it is working for me. > I will retry then > > stef

Sept. 19, 2008

Re: [Pharo-project] Image size

by StÃ©phane Ducasse

did you flush the changesets ? because it keeps a reference also to any changes. Stef On Sep 19, 2008, at 10:36 AM, Norbert Hartl wrote: > Hi, > > I have problems in understanding the image size of pharo. > I monitored it since we started and I did not recognize > a notably change. So I took a pharo 10073 and squeak 3.10.2 > for comparsion. yes frustrating after removing MVC and more. > > Amount classes, amount methods and lines of code are all 10% > less in pharo. But the image is approx. 0,5% - 1% smaller > than the squeak one. > > To clarify this. I closed all windows and did condenseChanges > and garbageCollect, flushed the monticello cache... > > What could be the reason for this? > > thanks, > > Norbert > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 19, 2008

Re: [Pharo-project] CS in pharo

by StÃ©phane Ducasse

what is the principal behind yoru atomic loading? - Another namespace - one become When we talk about atomic loading we mean that we should be able to change the code of a compiler while this one is currently compiling the changes that should loaded. Similarly, we should be able to modify the method that is currently been executed and showing the progress bar. Stef On Sep 19, 2008, at 10:06 AM, Joseph Pelrine wrote: > Hi Stef, > > StÃ©phane Ducasse wrote: >>> We have two important fixes: compiler fixes and trait that are in >>> Changesets or cannot be loaded (in the case of the compiler >>> with MC). >>> I suggest for now to add them as changesets >>> Then we should keep the Compiler package to evaluate if MC1.6 >>> can be used. >>> I asked matthew to see if he can load the package. >>> >>> I still believe that having atomic loading in pharo is important. > I had atomic loading working in Squeak ca. 10 years ago, and I'm > currently getting it working in Pharo, because I need it for a > project I'm working on. As I told you, I'm quite happy to give it to > you if you want to use it. > > Cheers > -- > Joseph Pelrine [ | ] > MetaProg GmbH > Email: jpelrine(a)metaprog.com > Web: http://www.metaprog.com > > You don't become enormously successful without encountering some > really interesting problems. > - Mark Victor Hansen > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 19, 2008

Re: [Pharo-project] CS in pharo

by StÃ©phane Ducasse

Ok our concern is that we cannot throw away our current architecture squeaksource and so on. Since this is a really important communication medium within the squeak community. But we will see. Stef On Sep 19, 2008, at 10:06 AM, Joseph Pelrine wrote: > Hi Stef, > > StÃ©phane Ducasse wrote: >>> We have two important fixes: compiler fixes and trait that are in >>> Changesets or cannot be loaded (in the case of the compiler >>> with MC). >>> I suggest for now to add them as changesets >>> Then we should keep the Compiler package to evaluate if MC1.6 >>> can be used. >>> I asked matthew to see if he can load the package. >>> >>> I still believe that having atomic loading in pharo is important. > I had atomic loading working in Squeak ca. 10 years ago, and I'm > currently getting it working in Pharo, because I need it for a > project I'm working on. As I told you, I'm quite happy to give it to > you if you want to use it. > > Cheers > -- > Joseph Pelrine [ | ] > MetaProg GmbH > Email: jpelrine(a)metaprog.com > Web: http://www.metaprog.com > > You don't become enormously successful without encountering some > really interesting problems. > - Mark Victor Hansen > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 19, 2008

Re: [Pharo-project] 10073 error

by StÃ©phane Ducasse

May be got an hiccup bvecause it is working for me. I will retry then stef On Sep 19, 2008, at 10:01 AM, Marcus Denker wrote: > > On 19.09.2008, at 09:19, StÃ©phane Ducasse wrote: > >> Hi >> >> I took 10072 and pressed update. >> After 10 or 15 min I got >> >> DoIt ^ server aborted early >> >> So may be the server stopped in the middle. >> > > I think gforge was down this morning... > > Marcus > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 19, 2008

[Pharo-project] Image size

by Norbert Hartl

Hi, I have problems in understanding the image size of pharo. I monitored it since we started and I did not recognize a notably change. So I took a pharo 10073 and squeak 3.10.2 for comparsion. Amount classes, amount methods and lines of code are all 10% less in pharo. But the image is approx. 0,5% - 1% smaller than the squeak one. To clarify this. I closed all windows and did condenseChanges and garbageCollect, flushed the monticello cache... What could be the reason for this? thanks, Norbert

Sept. 19, 2008

Re: [Pharo-project] CS in pharo

by Joseph Pelrine

Hi Stef, StÃ©phane Ducasse wrote: >> We have two important fixes: compiler fixes and trait that are in >> Changesets or cannot be loaded (in the case of the compiler >> with MC). >> I suggest for now to add them as changesets >> Then we should keep the Compiler package to evaluate if MC1.6 can >> be used. >> I asked matthew to see if he can load the package. >> >> I still believe that having atomic loading in pharo is important. I had atomic loading working in Squeak ca. 10 years ago, and I'm currently getting it working in Pharo, because I need it for a project I'm working on. As I told you, I'm quite happy to give it to you if you want to use it. Cheers -- Joseph Pelrine [ | ] MetaProg GmbH Email: jpelrine(a)metaprog.com Web: http://www.metaprog.com You don't become enormously successful without encountering some really interesting problems. - Mark Victor Hansen

Sept. 19, 2008