- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Memory Object Visualization

by Alexandre Bergel

It took about 10 minutes to profile and get the visualization. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Apr 23, 2015, at 10:17 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Nice. How fast is this? > > Doru > > On Thu, Apr 23, 2015 at 3:15 PM, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > Hi! > > Some of you may be interesting into this. > > We are currently working on a memory profiler. Our profiler snapshots a graph of objects. Visualizing them is then pretty easy. These pictures represent the graph of objects obtained by doing a system complexity (do it "RTGeneralExample new systemComplexity"). After the execution, 9070 objects are present in memory. These objects are naturally interconnected. > > The visualization clearly show the interaction between different components. A is the Trachel component, a low layer graphic library. B is Roassal, a high level graphic framework. Roassal highly depends on Trachel. Statically Trachel does not depends on Roassal, however, they are during the execution. C are instances of RTGroup, which is a dedicated collection used in Roassal. The system complexity has been open in Glamour, so D are the Glamour components. E are event related objects, mainly instance of the Announcer class (each RTElement and TRShape share a unique Announcer). F are classes (i.e., instances of the Color class). G are 2d coordinates (i.e., instances of the Point class). > > Thanks Alejandro Infante for this! > <Legend.png> > > Likes are always appreciated: https://www.facebook.com/ObjectProfile/posts/832387470181185 <https://www.facebook.com/ObjectProfile/posts/832387470181185> > :-) > > Cheers, > Alejandro & Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

April 23, 2015

Why is ZeroConf Repo moved?

by stephan

AFAIK, we still don't have a working git workflow, so why is development moved to github? I'm fine with duplication, less with making it impossible to contribute. Stephan

April 23, 2015

Re: [Pharo-dev] Memory Object Visualization

by Tudor Girba

Nice. How fast is this? Doru On Thu, Apr 23, 2015 at 3:15 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Some of you may be interesting into this. > > We are currently working on a memory profiler. Our profiler snapshots a > graph of objects. Visualizing them is then pretty easy. These pictures > represent the graph of objects obtained by doing a system complexity (do it > "RTGeneralExample new systemComplexity"). After the execution, 9070 objects > are present in memory. These objects are naturally interconnected. > > The visualization clearly show the interaction between different > components. A is the Trachel component, a low layer graphic library. B is > Roassal, a high level graphic framework. Roassal highly depends on Trachel. > Statically Trachel does not depends on Roassal, however, they are during > the execution. C are instances of RTGroup, which is a dedicated collection > used in Roassal. The system complexity has been open in Glamour, so D are > the Glamour components. E are event related objects, mainly instance of the > Announcer class (each RTElement and TRShape share a unique Announcer). F > are classes (i.e., instances of the Color class). G are 2d coordinates > (i.e., instances of the Point class). > > Thanks Alejandro Infante for this! > > Likes are always appreciated: > https://www.facebook.com/ObjectProfile/posts/832387470181185 > :-) > > Cheers, > Alejandro & Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- www.tudorgirba.com "Every thing has its own flow"

April 23, 2015

Memory Object Visualization

by Alexandre Bergel

Hi! Some of you may be interesting into this. We are currently working on a memory profiler. Our profiler snapshots a graph of objects. Visualizing them is then pretty easy. These pictures represent the graph of objects obtained by doing a system complexity (do it "RTGeneralExample new systemComplexity"). After the execution, 9070 objects are present in memory. These objects are naturally interconnected. The visualization clearly show the interaction between different components. A is the Trachel component, a low layer graphic library. B is Roassal, a high level graphic framework. Roassal highly depends on Trachel. Statically Trachel does not depends on Roassal, however, they are during the execution. C are instances of RTGroup, which is a dedicated collection used in Roassal. The system complexity has been open in Glamour, so D are the Glamour components. E are event related objects, mainly instance of the Announcer class (each RTElement and TRShape share a unique Announcer). F are classes (i.e., instances of the Color class). G are 2d coordinates (i.e., instances of the Point class). Thanks Alejandro Infante for this! Likes are always appreciated: https://www.facebook.com/ObjectProfile/posts/832387470181185 <https://www.facebook.com/ObjectProfile/posts/832387470181185> :-) Cheers, Alejandro & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 23, 2015

Re: [Pharo-dev] Versionner repository moved to PharoExtras

by Christophe Demarey

Thanks, Done! Le 23 avr. 2015 Ã 14:03, Sean P. DeNigris a Ã©crit : > demarey wrote >> I just moved the Versionner repository from >> http://smalltalkhub.com/#!/~demarey/Versionner/ to >> http://smalltalkhub.com/#!/~PharoExtras/Versionner/. >> It will ease contributions and it will be easier to find with other tools >> / library of Pharo. > > Thanks, Christophe! > Maybe change the move notice in the old repo to something more pronounced > like http://smalltalkhub.com/#!/~Pharo/ZeroConf : > > MOVED TO GITHUB: https://github.com/pharo-project/pharo-zeroconf > <https://github.com/pharo-project/pharo-zeroconf> > > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Versionner-repository-moved-to-PharoExtras-tp4821378p… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 23, 2015

[pharo-project/pharo-core] 514e3f: 50008

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 514e3fa9aef50be8b7df2c54ebff8eac878c22c8 https://github.com/pharo-project/pharo-core/commit/514e3fa9aef50be8b7df2c54… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-23 (Thu, 23 Apr 2015) Changed paths: A Komitter.package/RemotesManager.class/instance/accessing/title.st M Komitter.package/RemotesManager.class/instance/api/selectedRemotes_.st R Komitter.package/RemotesManager.class/instance/api/title.st M Komitter.package/RemotesManager.class/instance/private/selected_changed_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script616.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script617.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50007.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50008.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50008 15384 kommiter throws DNU when browsing remotes https://pharo.fogbugz.com/f/cases/15384 http://files.pharo.org/image/50/50008.zip

April 23, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50008 Home: https://github.com/pharo-project/pharo-core

April 23, 2015

Re: [Pharo-dev] Group and category of Small Lint rules

by Marcus Denker

Yes! https://pharo.fogbugz.com/f/cases/14454/Unify-group-and-category On Thu, Apr 23, 2015 at 2:36 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi guys. > > Each SmallLint rule has two methods: #group and #category. Critics browser > uses #categoryâ¦ Can we have only one? > > Uko > -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

April 23, 2015

Group and category of Small Lint rules

by Yuriy Tymchuk

Hi guys. Each SmallLint rule has two methods: #group and #category. Critics browser uses #categoryâ¦ Can we have only one? Uko

April 23, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40610 Home: https://github.com/pharo-project/pharo-core

April 23, 2015