- Pharo-users - lists.pharo.org

Re: [Pharo-users] Garbage collector & Memory Profiling

by Henrik Johansen

On Jul 31, 2013, at 3:23 , Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > As far as I know, that's not possible in Pharo unless you explicitly register the desired objects in "WeakRegistry default" or similar (and implement #finalize). > I think is the closest you have. > > Cheers, A few clarifications: - You can use a non-default WeakRegistry (usually one specific to your domain, to avoid cluttering of the default one) - You can specify a custom executor (any object which implements #finalize), rather than implement #finalize on objects you're interested in. obj := Object new. executor := ObjectFinalizer receiver: Transcript selector: #show: argument: 'Object GC''d!'. myReg := WeakRegistry new. myReg add: obj executor: executor. obj := nil. Smalltalk garbageCollect. Cheers, Henry

July 31, 2013

Re: [Pharo-users] Garbage collector & Memory Profiling

by Mariano Martinez Peck

As far as I know, that's not possible in Pharo unless you explicitly register the desired objects in "WeakRegistry default" or similar (and implement #finalize). I think is the closest you have. Cheers, On Tue, Jul 30, 2013 at 5:00 PM, Alejandro Infante < alejandroinfante91(a)gmail.com> wrote: > Hello, > We are currently working on memory profiling and we are having troubles to > detect when an object is garbage collected. > > Any ideas? > > Thanks for the help, > Alejandro Infante > -- Mariano http://marianopeck.wordpress.com

July 31, 2013

Re: [Pharo-users] Pharo performance

by phil＠highoctane.be

Yes, as discussed, I am pushing Pharo and discussing business in the open just doesn't work for me.

July 30, 2013

Re: [Pharo-users] Pharo performance

by StÃ©phane Ducasse

yes normally there is one :) Now I will check who is in. What we should pay attention is that we are not really in favor of private discussions (even if I understand it fr business it is important). If you think that this would be good we can create a private business list. Stef > BTW, is there any special consortium list where we can discuss business out of the public eye? > > --- > Philippe Back > Dramatic Performance Improvements > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 > Mail:phil@highoctane.be | Web: http://philippeback.eu > Blog: http://philippeback.be | Twitter: @philippeback > Youtube: http://www.youtube.com/user/philippeback/videos > > High Octane SPRL > rue cour Boisacq 101 | 1301 Bierges | Belgium > > Featured on the Software Process and Measurement Cast > http://spamcast.libsyn.com > Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller > > > > > On Tue, Jul 30, 2013 at 11:02 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> > > > > You could try: > > > > | floats | > > floats := (1 to: 200000) collect: #asFloat. > > [ FloatPrintPolicy > > value: InexactFloatPrintPolicy new > > during: [ > > String new: 1500000 streamContents: [ :stream | > > floats do: [ :each | each printOn: stream ] ] ] ] timeToRun > > > > => 796 ms > > > > I haven't looked at the Postgresql driver in detail, but I would guess that PostgresV2 reads from a String somewhere, which is slow unless care is taken, while psycopg probably does a binary read. That last thing can be done in Pharo as well, but not if the driver is text based somehow. > > > > You are right: Pharo should definitively be in the same range as other dynamically typed languages. But dynamic languages are dangerous: user become lazy / ignorant about performance. > > > > Thanks for pushing this. > > +1 > we need more people to profile and look at these aspects. > I can tell you that we are all working like crazy to improve the system and I hope that one of these days we will have > real regression tests. But well you know it takes a lot of time. > > Stef > >

July 30, 2013

Re: [Pharo-users] Pharo performance

by phil＠highoctane.be

BTW, is there any special consortium list where we can discuss business out of the public eye? --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Featured on the Software Process and Measurement Cast http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Tue, Jul 30, 2013 at 11:02 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > >> > > > > You could try: > > > > | floats | > > floats := (1 to: 200000) collect: #asFloat. > > [ FloatPrintPolicy > > value: InexactFloatPrintPolicy new > > during: [ > > String new: 1500000 streamContents: [ :stream | > > floats do: [ :each | each printOn: stream ] ] ] ] timeToRun > > > > => 796 ms > > > > I haven't looked at the Postgresql driver in detail, but I would guess > that PostgresV2 reads from a String somewhere, which is slow unless care is > taken, while psycopg probably does a binary read. That last thing can be > done in Pharo as well, but not if the driver is text based somehow. > > > > You are right: Pharo should definitively be in the same range as other > dynamically typed languages. But dynamic languages are dangerous: user > become lazy / ignorant about performance. > > > > Thanks for pushing this. > > +1 > we need more people to profile and look at these aspects. > I can tell you that we are all working like crazy to improve the system > and I hope that one of these days we will have > real regression tests. But well you know it takes a lot of time. > > Stef > >

July 30, 2013

Re: [Pharo-users] [Moose-dev] [ann] a snappier snapshotcello

by StÃ©phane Ducasse

sweet! I should find some time to use it on some projects I have. Stef On Jul 30, 2013, at 11:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > A new version of Snapshotcello is now reachable from your Pharo 2.0 image. Besides snapshotting the current version, you now get the possibility of: > - marking the new version as stable, > - committing the configuration package, and > - pushing the package to the official Pharo repository. > > Here is an example: > Snapshotcello new > configurationClass: ConfigurationOfSnapshotcello; > sourceVersion: #development; > targetVersion: '1.4-snapshot'; > snapshot; > makeStableFor: #'pharo2.x'; > commit; > pushToPharo20Repository > > A more detailed description can be found here: > http://www.tudorgirba.com/blog/snappier-snapshotcello > > We can certainly improve this, and it would be great to have a similar mechanism integrated into Metacello. But, in the meantime, I find myself for the first time literally one do-it away from distributing projects that are developed without much constraints. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

July 30, 2013

Re: [Pharo-users] Pharo performance

by StÃ©phane Ducasse

>> > > You could try: > > | floats | > floats := (1 to: 200000) collect: #asFloat. > [ FloatPrintPolicy > value: InexactFloatPrintPolicy new > during: [ > String new: 1500000 streamContents: [ :stream | > floats do: [ :each | each printOn: stream ] ] ] ] timeToRun > > => 796 ms > > I haven't looked at the Postgresql driver in detail, but I would guess that PostgresV2 reads from a String somewhere, which is slow unless care is taken, while psycopg probably does a binary read. That last thing can be done in Pharo as well, but not if the driver is text based somehow. > > You are right: Pharo should definitively be in the same range as other dynamically typed languages. But dynamic languages are dangerous: user become lazy / ignorant about performance. > > Thanks for pushing this. +1 we need more people to profile and look at these aspects. I can tell you that we are all working like crazy to improve the system and I hope that one of these days we will have real regression tests. But well you know it takes a lot of time. Stef

July 30, 2013

[ann] a snappier snapshotcello

by Tudor Girba

Hi, A new version of Snapshotcello is now reachable from your Pharo 2.0 image. Besides snapshotting the current version, you now get the possibility of: - marking the new version as stable, - committing the configuration package, and - pushing the package to the official Pharo repository. Here is an example: Snapshotcello new configurationClass: ConfigurationOfSnapshotcello; sourceVersion: #development; targetVersion: '1.4-snapshot'; snapshot; makeStableFor: #'pharo2.x'; commit; pushToPharo20Repository A more detailed description can be found here: http://www.tudorgirba.com/blog/snappier-snapshotcello We can certainly improve this, and it would be great to have a similar mechanism integrated into Metacello. But, in the meantime, I find myself for the first time literally one do-it away from distributing projects that are developed without much constraints. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

July 30, 2013

Re: [Pharo-users] Little tutorial on customizing zero conf scripts

by StÃ©phane Ducasse

We could add this as part of the ZeroConf chapter :) But I guess that first the book should get out :) Stef > Hey guys! > > inspired by the work of Camillo and Andrei customizing the ZeroConf scripts for moose, I did the same for my phd project and wrote a little tiny shy tutorial about it. > > http://playingwithobjects.wordpress.com/2013/07/30/customizing-zeroconf-scr… > > Hope it's helpful for somebody :) > > Guille

July 30, 2013

Re: [Pharo-users] Git filetree workflow

by StÃ©phane Ducasse

We know that changing version can be painful but just consider that you are working with a nearly 3 years old system. stef On Jul 30, 2013, at 4:41 PM, joerick <joerick(a)mac.com> wrote: > Oh, I'm having trouble adding a gitfiletree repository, do you support Pharo > 1.4? > > > > -- > View this message in context: http://forum.world.st/Git-filetree-workflow-tp4701465p4701541.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

July 30, 2013