- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Manuia Memory Monitor

by Henrik Johansen

On May 31, 2010, at 3:17 28PM, Alexandre Bergel wrote: > Hi! > > Between two latexing session, I did a 3 hours long coding session. I produced Manuia, a real-time memory monitor. I attached a screenshot to this email. > You can try it by: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSpy'; > load. > (Smalltalk at: #ConfigurationOfSpy) perform: #loadDefault > > > If you use a Pharo 1.1 then world menu/tools/Manuia Memory Monitor . Else, evaluate "ManuiaMonitor new open" > Green curve is about the memory consumption: when it goes up, when you consuming memory. Vertical bars indicate that at least 10 incremental garbage collect was realized. > > There is a probe class button. Click on it, enter the name of a class, then you can see the evolution of the number of instances. > > It is just a small experiment I did. I haven't got the time to intensively use it. Feedbacks are very welcome. > > Cheers, > Alexandre > -- Works just fine not loading the entire Spy/Mondrian packages as well... Personally I'd really like to see something like this, combined with some of the textual data from Debug -> VM Statistics + Space left as a core tool. :) Cheers, Henry

May 31, 2010

[Pharo-project] Fwd: [squeak-dev] traits

by Mariano Martinez Peck

Hi Norbert: I am not sure the current situation in Squeak but in Pharo I know it is used in some places. I think in some Collection testing and Nile framework...but I am not sure. Anyone can help? Cheers Mariano ---------- Forwarded message ---------- From: Norbert Fortelny <norbert.fortelny(a)gmail.com> Date: Wed, May 19, 2010 at 5:17 PM Subject: [squeak-dev] traits To: squeak-dev <squeak-dev(a)lists.squeakfoundation.org> Could anyone point me to sample code using traits in squeak. Poked around a bit but couldn't find anything. thanks and sorry if that is inappropriate here. Norbert

May 31, 2010

Re: [Pharo-project] Manuia Memory Monitor

by Mariano Martinez Peck

Alexandre: Is there a way (or will be in a future) a way to script and customize it ? Suppose I want to trace several things, not only the amount of memory used. I would love to be able to define my own curves and have several at the same time. Maybe what I need is just that graph but totally customized for me. Any hints? Thanks in advance, Mariano On Mon, May 31, 2010 at 3:50 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi Alexandre. This is very interesting for me. > > I just test it a little. I am quite intrigued to know if the attached > screenshots are normal. > > I just did nothing. I mean NOTHING in the image, while Manuia was running. > I just left the mouse and keyboard doing nothing. > > First was picture 11 and then 13. > > Another question: what is the red curve in your screenshot? I don't have > it. > > Thanks > > Mariano > > 2010/5/31 Alexandre Bergel <alexandre.bergel(a)inria.fr> > >> Hi! >> >> Between two latexing session, I did a 3 hours long coding session. I >> produced Manuia, a real-time memory monitor. I attached a screenshot to this >> email. >> You can try it by: >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfSpy'; >> load. >> (Smalltalk at: #ConfigurationOfSpy) perform: #loadDefault >> >> >> If you use a Pharo 1.1 then world menu/tools/Manuia Memory Monitor . Else, >> evaluate "ManuiaMonitor new open" >> Green curve is about the memory consumption: when it goes up, when you >> consuming memory. Vertical bars indicate that at least 10 incremental >> garbage collect was realized. >> >> There is a probe class button. Click on it, enter the name of a class, >> then you can see the evolution of the number of instances. >> >> It is just a small experiment I did. I haven't got the time to intensively >> use it. Feedbacks are very welcome. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

May 31, 2010

Re: [Pharo-project] Manuia Memory Monitor

by Mariano Martinez Peck

On Mon, May 31, 2010 at 4:06 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >I just did nothing. I mean NOTHING in the image, while Manuia was running > > Even if YOU do nothing in an image there are processes running > (including Manuia itself) creating objects that get collected. > > Good point. Maybe in a finer release, it could exclude its own usage from the graphs? > >Another question: what is the red curve in your screenshot? I don't have > >it. > > Click on "Probe class" and enter a class name, e.g. "Array" > As Alexandre wrote: red line = evolution of the number of instances > > Uff I didn't read it. Thanks > two things: > - "Manuia Memory Monitor" => I would just call it "Memory Monitor" > (at least in the menu) > +1 > - When installed there is also a "MOEasel" menu entry appearing > from Mondrian => gives a DNU when clicked > > Bye > T. > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 31, 2010

[Pharo-project] Manuia Memory Monitor

by Torsten Bergmann

>I just did nothing. I mean NOTHING in the image, while Manuia was running Even if YOU do nothing in an image there are processes running (including Manuia itself) creating objects that get collected. >Another question: what is the red curve in your screenshot? I don't have >it. Click on "Probe class" and enter a class name, e.g. "Array" As Alexandre wrote: red line = evolution of the number of instances two things: - "Manuia Memory Monitor" => I would just call it "Memory Monitor" (at least in the menu) - When installed there is also a "MOEasel" menu entry appearing from Mondrian => gives a DNU when clicked Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 31, 2010

Re: [Pharo-project] Manuia Memory Monitor

by Mariano Martinez Peck

Hi Alexandre. This is very interesting for me. I just test it a little. I am quite intrigued to know if the attached screenshots are normal. I just did nothing. I mean NOTHING in the image, while Manuia was running. I just left the mouse and keyboard doing nothing. First was picture 11 and then 13. Another question: what is the red curve in your screenshot? I don't have it. Thanks Mariano 2010/5/31 Alexandre Bergel <alexandre.bergel(a)inria.fr> > Hi! > > Between two latexing session, I did a 3 hours long coding session. I > produced Manuia, a real-time memory monitor. I attached a screenshot to this > email. > You can try it by: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSpy'; > load. > (Smalltalk at: #ConfigurationOfSpy) perform: #loadDefault > > > If you use a Pharo 1.1 then world menu/tools/Manuia Memory Monitor . Else, > evaluate "ManuiaMonitor new open" > Green curve is about the memory consumption: when it goes up, when you > consuming memory. Vertical bars indicate that at least 10 incremental > garbage collect was realized. > > There is a probe class button. Click on it, enter the name of a class, then > you can see the evolution of the number of instances. > > It is just a small experiment I did. I haven't got the time to intensively > use it. Feedbacks are very welcome. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2010

[Pharo-project] Manuia Memory Monitor

by Alexandre Bergel

Hi! Between two latexing session, I did a 3 hours long coding session. I produced Manuia, a real-time memory monitor. I attached a screenshot to this email. You can try it by: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSpy'; load. (Smalltalk at: #ConfigurationOfSpy) perform: #loadDefault If you use a Pharo 1.1 then world menu/tools/Manuia Memory Monitor . Else, evaluate "ManuiaMonitor new open" Green curve is about the memory consumption: when it goes up, when you consuming memory. Vertical bars indicate that at least 10 incremental garbage collect was realized. There is a probe class button. Click on it, enter the name of a class, then you can see the evolution of the number of instances. It is just a small experiment I did. I haven't got the time to intensively use it. Feedbacks are very welcome. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 31, 2010

Re: [Pharo-project] Status of Alien FFI in windows Re: plan for 1.1

by Igor Stasenko

2010/5/31 Mariano Martinez Peck <marianopeck(a)gmail.com>: > So...which is the status of Alien FFI ? > > I remember Marco Schmidt did the first work of running FFI in windows...then > I think David was integrating such changes in VMMaker.. > > so, it is ready ? can be generate the plugin using VMMaker for winwows and > it just works? > > Thanks for any update > I managed to build Alien plugin for win32. And it didn't built without manual sources patching. I described it in another thread, not long ago. Try search mail archives. > Mariano > > 2010/5/26 Guillermo Polito <guillermopolito(a)gmail.com> >> >> Where can I read something about Alien?Â I can give a little hand for the >> windows part :). >> >> On Wed, May 26, 2010 at 11:12 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >> wrote: >>> >>> Stef, >>> >>> I am more concerned about Alien on Linux, which is not working. Â Beyond >>> that, I want to learn more about how to make calls using Alien; the more I >>> read, the more I have my doubts about its ease of use. Â I will gladly eat >>> those words if it's easy to use. >>> >>> Bill >>> >>> >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse >>> [stephane.ducasse(a)inria.fr] >>> Sent: Wednesday, May 26, 2010 10:04 AM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] plan for 1.1 >>> >>> yes this is good point. >>> I would like to have alien or ffi in 1.1. Now I do not know the status of >>> Alien on windows. >>> >>> On May 26, 2010, at 2:52 PM, Schwab,Wilhelm K wrote: >>> >>> > Stef, >>> > >>> > My initial reaction to 1.1's approaching release was "where are the >>> > callbacks/aliens?" Â Sig appears to be offering some competition to Alien. >>> > Â If he/we can provide a comprehensive and convenient way to make calls, do >>> > callbacks, additionally put calls onto other OS threads, and do all of this >>> > on the three major platforms, then it could easily turn out the best option >>> > for external interfacing. >>> > >>> > I am happy to see us take time to get it right. Â My only concern would >>> > be that we not fall into a pattern of leaving out the difficult things that >>> > we set out to accomplish with a given release. Â Since 1.1 is approaching >>> > releasable form and FFI/Alien/NB is unclear at present, a release makes >>> > sense. >>> > >>> > Short answer: sure, whatever you say :) >>> > >>> > Bill >>> > >>> > >>> > ________________________________________ >>> > From: pharo-project-bounces(a)lists.gforge.inria.fr >>> > [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse >>> > [stephane.ducasse(a)inria.fr] >>> > Sent: Wednesday, May 26, 2010 4:20 AM >>> > To: Pharo Development >>> > Subject: [Pharo-project] plan for 1.1 >>> > >>> > Hi guys >>> > >>> > we were discussing how we can handle 1.1 and the flux of good changes. >>> > Here is the proposal: >>> > Â Â Â Â we take two or three weeks to let people try their code in 1.1 >>> > beta >>> > Â Â Â Â we integrate fixes that are important or easy >>> > Â Â Â Â then we wait one week >>> > Â Â Â Â then we launch 1.1 rc and 1.2 unstable >>> > >>> > does this plan look ok for you? >>> > The key point is that we want to avoid to have a pile of changes >>> > pending because they can rot easily. >>> > >>> > Stef >>> > _______________________________________________ >>> > 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 >>> >>> >>> _______________________________________________ >>> 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 >> >> >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

May 31, 2010

Re: [Pharo-project] Recompile all in ImageForDevelopers ?

by laurent laffont

2010/5/31 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > 2010/5/31 laurent laffont <laurent.laffont(a)gmail.com> > > 2010/5/31 Mariano Martinez Peck <marianopeck(a)gmail.com> >> >>> Hi folks. The official Pharo 1.0 has a little bug that you can see here: >>> >>> http://code.google.com/p/pharo/issues/detail?id=2341 >>> >>> In order to avoid such problems, I though about evaluating "Compiler >>> recompileAll" during the ImageForDeveloper >> install method >>> With this, when I or you are using ConfigurationOfPharo to build a Dev >>> image, you will automatically realize there is a problem. >>> >>> What do you think? >>> >> >> How much time does it take ? >> > > > MessageTally time: [Compiler recompileAll] -> 116142 > > so...2 minutes ;) > OK, so not very long. I remember the bad experience from condensing changes :). Then I agree for betas / rc images, not sure about final. Laurent > > >> >> Laurent Laffont >> >> http://pharocasts.blogspot.com/ >> http://magaloma.blogspot.com/ >> >> >>> >>> Cheers >>> >>> Mariano >>> >>> _______________________________________________ >>> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2010

Re: [Pharo-project] Image Lockdown/Deployment mode

by Mariano Martinez Peck

On Wed, May 26, 2010 at 5:23 PM, Gary Chambers <gazzaguru2(a)btinternet.com>wrote: > Mostly done via #disableProgrammerFacilities, > though I note it is now deprecated in Pharo... > > Also, deactivating ProjectLauncher takes care of the startup script thing. > > Gary, it would be really cool to have a section in the collaborative book explaining this ;) I wasn't aware of it, it is pretty cool. Thanks Mariano > Regards, Gary > > ----- Original Message ----- From: "StÃ©phane Ducasse" < > stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, May 26, 2010 3:02 PM > Subject: Re: [Pharo-project] Image Lockdown/Deployment mode > > > > Good question we need that!!!! > We were thinking about that with noury for 1.0 and got distracted. > This is really important. Any step in that direction is really welcome > > Does Pharo currently provide support for a deployment mode/image >> locking mode? >> >> I think of the following scenario: >> ================================== >> If one builds a rich (client) app for a customer based on Pharo >> (I mean a real app, no Smalltalk tool - for instance a game or >> a commercial app) he may want to: >> >> - lock the image so nobody is able to hit Cmd-. >> - exchange the Walkback to display a custom dialog instead >> of proving debugger access to the end user. Do we provide a >> hook already? >> - replace world menu with a custom menu. Do we provide a >> hook already? >> - wants to disable code evaluation in edit fields using >> * menus (no doIt, printIt, inspectIt just cut, copy, paste) >> * keyboard (Cmd-d, ...) >> - wants to disable Halos >> - prevent reading scripts/projects at startup so nobody is >> able to hijack the image and get access to the code >> - disable the dependency on source and changes file >> >> Maybe this locking facility can be reenabled after entering a >> password so a developer can still debug in the customers environment. >> (I remember Andreas said that they protect the Teleplace >> image and save the password hashed in image). >> >> Maybe Gary can share his experience to lock the "Pinesoft â MBagger" >> image or others how they lock down their image. >> >> Either we provide such a (switchable) mode in the default image >> or give a guide in the pharo book on how to restrict end user >> access to the Smalltalk environment in deployed applications. >> >> Yes - we provide a #cleanUpForProduction method - but this is >> more to reduce size. >> >> Maybe the old "Lockdown" package could be a start: >> http://wiki.squeak.org/squeak/518 >> >> I think of a loadable package "ImageLocker" with a class >> that can set/unset the appropriate preferences and provide >> alternative error handlers, menues, ... >> >> Any comments? >> >> Thx >> T. >> >> BTW: I remember having a hard time with the "deployment step" in most >> commercial environments due to "striping" the image. Now this >> is partly adressed by building images bottom to top using >> Metacello now. One could load his app based on a core without >> the extended dev-tools. >> >> But Pharo should really care to also easily disable developer >> facilities so developers may use it as the platform for >> their next project. >> >> >> -- >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >> >> _______________________________________________ >> 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2010