June 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

Stefan note also that ConfigurationOfBenchmarking - refers to SqueakSource - refers to Scripting but scripting is not in the smalltalkhub/StefanMarr/SMark/main Stef

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

Ok I will load the configuration file. It would be good to rename the configuration: ConfigurationOfSMark like that it is consistent with the project name. I thought that ConfigurationOfBenchmarking was something else. Stef On Jun 16, 2013, at 8:47 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > there is no ScriptConsole but I imagine that using Transcript is ok. > > On Jun 16, 2013, at 8:45 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> Stefan >> >> for your info >> SMarkHarness run: {'SMarkHarness'. 'SMarkLoops.benchIntLoop'. 1. 1. 5} >> does not work. >> >> Stef >> >> >>> Hi Stef: >>> >>> On 16 Jun 2013, at 12:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>> I would like to know how to use SMark and document it. >>>>> Do you have a start of a blog/doc/slide that I can use as a start? >>> >>> I am not aware of a blog post or similar things. >>> >>> All we got at the moment are class comments. >>> >>> The entry class is the benchmark harness: SMarkHarness. >>> >>> The benchmark SMarkSuite has also a comment, which gives minimal information of how to use it. >>> Note that I use SMark mostly from the command line. So, it only has a limited set of convenience methods. >>> Most of the time, I use `SMarkHarness run:` as in the example below. >>> >>>> I started to read the code (and its self-documentation aspect is not totally there). >>>> Stefan I started to comment the code so are you interested in the commits? >>> >>> Sure, they can always be improved. Contributions are welcome. >>> >>> >>>> (SMarkLoops new runOnly: #benchFloatLoop) run >>> >>> Ehm, where did you find that? That is not supposed to work currently, because the benchmark suite is not independent of the rest of the infrastructure and needs to be initialized properly (most notably, it needs a benchmark runner, which actually executes the benchmarks, we use that indirection for instance to warm up the CogVM properly). >>> >>> `SMarkLoops run` is supposed to work. >>> If you want a convenience method like #runOnly: it should be implemented on the class-side like #run. >>> >>> On the other hand, following the class comment of SMarkHarness, you can also use: >>> >>> SMarkHarness run: {'SMarkHarness'. 'SMarkLoops.benchFloatLoop'. 10. 1. 500} >>> >>> But you probably want to open a transcript first, and then execute: `ScriptConsole outputToTranscript: true.`. >>> Otherwise, you will probably not see the output, because it goes normally only to stdout on the command line. >>> >>> Best regards >>> Stefan >>> >>> >>> >>> >>> -- >>> Stefan Marr >>> Software Languages Lab >>> Vrije Universiteit Brussel >>> Pleinlaan 2 / B-1050 Brussels / Belgium >>> http://soft.vub.ac.be/~smarr >>> Phone: +32 2 629 2974 >>> Fax: +32 2 629 3525 >>> >>> >> >

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

there is no ScriptConsole but I imagine that using Transcript is ok. On Jun 16, 2013, at 8:45 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > Stefan > > for your info > SMarkHarness run: {'SMarkHarness'. 'SMarkLoops.benchIntLoop'. 1. 1. 5} > does not work. > > Stef > > >> Hi Stef: >> >> On 16 Jun 2013, at 12:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> I would like to know how to use SMark and document it. >>>> Do you have a start of a blog/doc/slide that I can use as a start? >> >> I am not aware of a blog post or similar things. >> >> All we got at the moment are class comments. >> >> The entry class is the benchmark harness: SMarkHarness. >> >> The benchmark SMarkSuite has also a comment, which gives minimal information of how to use it. >> Note that I use SMark mostly from the command line. So, it only has a limited set of convenience methods. >> Most of the time, I use `SMarkHarness run:` as in the example below. >> >>> I started to read the code (and its self-documentation aspect is not totally there). >>> Stefan I started to comment the code so are you interested in the commits? >> >> Sure, they can always be improved. Contributions are welcome. >> >> >>> (SMarkLoops new runOnly: #benchFloatLoop) run >> >> Ehm, where did you find that? That is not supposed to work currently, because the benchmark suite is not independent of the rest of the infrastructure and needs to be initialized properly (most notably, it needs a benchmark runner, which actually executes the benchmarks, we use that indirection for instance to warm up the CogVM properly). >> >> `SMarkLoops run` is supposed to work. >> If you want a convenience method like #runOnly: it should be implemented on the class-side like #run. >> >> On the other hand, following the class comment of SMarkHarness, you can also use: >> >> SMarkHarness run: {'SMarkHarness'. 'SMarkLoops.benchFloatLoop'. 10. 1. 500} >> >> But you probably want to open a transcript first, and then execute: `ScriptConsole outputToTranscript: true.`. >> Otherwise, you will probably not see the output, because it goes normally only to stdout on the command line. >> >> Best regards >> Stefan >> >> >> >> >> -- >> Stefan Marr >> Software Languages Lab >> Vrije Universiteit Brussel >> Pleinlaan 2 / B-1050 Brussels / Belgium >> http://soft.vub.ac.be/~smarr >> Phone: +32 2 629 2974 >> Fax: +32 2 629 3525 >> >> >

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

Stefan for your info SMarkHarness run: {'SMarkHarness'. 'SMarkLoops.benchIntLoop'. 1. 1. 5} does not work. Stef > Hi Stef: > > On 16 Jun 2013, at 12:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> I would like to know how to use SMark and document it. >>> Do you have a start of a blog/doc/slide that I can use as a start? > > I am not aware of a blog post or similar things. > > All we got at the moment are class comments. > > The entry class is the benchmark harness: SMarkHarness. > > The benchmark SMarkSuite has also a comment, which gives minimal information of how to use it. > Note that I use SMark mostly from the command line. So, it only has a limited set of convenience methods. > Most of the time, I use `SMarkHarness run:` as in the example below. > >> I started to read the code (and its self-documentation aspect is not totally there). >> Stefan I started to comment the code so are you interested in the commits? > > Sure, they can always be improved. Contributions are welcome. > > >> (SMarkLoops new runOnly: #benchFloatLoop) run > > Ehm, where did you find that? That is not supposed to work currently, because the benchmark suite is not independent of the rest of the infrastructure and needs to be initialized properly (most notably, it needs a benchmark runner, which actually executes the benchmarks, we use that indirection for instance to warm up the CogVM properly). > > `SMarkLoops run` is supposed to work. > If you want a convenience method like #runOnly: it should be implemented on the class-side like #run. > > On the other hand, following the class comment of SMarkHarness, you can also use: > > SMarkHarness run: {'SMarkHarness'. 'SMarkLoops.benchFloatLoop'. 10. 1. 500} > > But you probably want to open a transcript first, and then execute: `ScriptConsole outputToTranscript: true.`. > Otherwise, you will probably not see the output, because it goes normally only to stdout on the command line. > > Best regards > Stefan > > > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

> Hi Stef: > > On 16 Jun 2013, at 12:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> I would like to know how to use SMark and document it. >>> Do you have a start of a blog/doc/slide that I can use as a start? > > I am not aware of a blog post or similar things. it is coming :) see the attachment. > All we got at the moment are class comments. > > The entry class is the benchmark harness: SMarkHarness. Ok I missed it. > The benchmark SMarkSuite has also a comment, which gives minimal information of how to use it. > Note that I use SMark mostly from the command line. So, it only has a limited set of convenience methods. > Most of the time, I use `SMarkHarness run:` as in the example below. what do you think about initializing the runner of a suite to the be the default one? This way we could do SmarkLoops new runBenchmark: #benchArrayAccess. What is the <omniUnenforced>? "Hint for the OMOP that it is part of the meta infrastructure" I kind of get that this is a kind of annotation for your phd thesis. > >> I started to read the code (and its self-documentation aspect is not totally there). >> Stefan I started to comment the code so are you interested in the commits? > > Sure, they can always be improved. Contributions are welcome. > > >> (SMarkLoops new runOnly: #benchFloatLoop) run > > Ehm, where did you find that? That is not supposed to work currently, because the benchmark suite is not independent of the rest of the infrastructure and needs to be initialized properly (most notably, it needs a benchmark runner, which actually executes the benchmarks, we use that indirection for instance to warm up the CogVM properly). Yes I saw > `SMarkLoops run` is supposed to work. > If you want a convenience method like #runOnly: it should be implemented on the class-side like #run. This is also what I thought. But since it was only on the class side I tried it on the intstance > > On the other hand, following the class comment of SMarkHarness, you can also use: > > SMarkHarness run: {'SMarkHarness'. 'SMarkLoops.benchFloatLoop'. 10. 1. 500} > > But you probably want to open a transcript first, and then execute: `ScriptConsole outputToTranscript: true.`. > Otherwise, you will probably not see the output, because it goes normally only to stdout on the command line. ok I will continue to read the code. > > Best regards > Stefan > > > > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by Stefan Marr

Hi Stef: On 16 Jun 2013, at 12:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> I would like to know how to use SMark and document it. >> Do you have a start of a blog/doc/slide that I can use as a start? I am not aware of a blog post or similar things. All we got at the moment are class comments. The entry class is the benchmark harness: SMarkHarness. The benchmark SMarkSuite has also a comment, which gives minimal information of how to use it. Note that I use SMark mostly from the command line. So, it only has a limited set of convenience methods. Most of the time, I use `SMarkHarness run:` as in the example below. > I started to read the code (and its self-documentation aspect is not totally there). > Stefan I started to comment the code so are you interested in the commits? Sure, they can always be improved. Contributions are welcome. > (SMarkLoops new runOnly: #benchFloatLoop) run Ehm, where did you find that? That is not supposed to work currently, because the benchmark suite is not independent of the rest of the infrastructure and needs to be initialized properly (most notably, it needs a benchmark runner, which actually executes the benchmarks, we use that indirection for instance to warm up the CogVM properly). `SMarkLoops run` is supposed to work. If you want a convenience method like #runOnly: it should be implemented on the class-side like #run. On the other hand, following the class comment of SMarkHarness, you can also use: SMarkHarness run: {'SMarkHarness'. 'SMarkLoops.benchFloatLoop'. 10. 1. 500} But you probably want to open a transcript first, and then execute: `ScriptConsole outputToTranscript: true.`. Otherwise, you will probably not see the output, because it goes normally only to stdout on the command line. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

thanks I will integrate it. Stef On Jun 16, 2013, at 8:00 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > actually that is related to a bug in 3.0 :/ > > => https://pharo.fogbugz.com/default.asp?10920 > > > On 2013-06-16, at 19:50, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> #profile: is supposed to open the profiler on the given benchmark. >> let me fix that :) >> >> On 2013-06-16, at 19:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> SMarkLoops profile: #benchArrayAccess >>> >>> does not work >>> >>> I was wondering if this is the class side version of runBenchmark: >>> >>> Stef >>> >>> >>> On Jun 16, 2013, at 12:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >>> >>>> I started to read the code (and its self-documentation aspect is not totally there). >>>> >>>> >>>> (SMarkLoops new runOnly: #benchFloatLoop) run >>>> >>>> Stefan I started to comment the code so are you interested in the commits? >>>> >>>> >>>> Stef >>>> >>>> >>>>> Hi camillo/Stefan >>>>> >>>>> I would like to know how to use SMark and document it. >>>>> Do you have a start of a blog/doc/slide that I can use as a start? >>>>> >>>>> I'm thinking that I could use the implementation of Trie of Benoit and the one of Cuis >>>>> as an example to do some benchs. >>>>> Since I'm not fluent in benchmarks, I think that this the occasion to learn. >>>>> >>>>> Stef >

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by Camillo Bruni

actually that is related to a bug in 3.0 :/ => https://pharo.fogbugz.com/default.asp?10920 On 2013-06-16, at 19:50, Camillo Bruni <camillobruni(a)gmail.com> wrote: > #profile: is supposed to open the profiler on the given benchmark. > let me fix that :) > > On 2013-06-16, at 19:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> SMarkLoops profile: #benchArrayAccess >> >> does not work >> >> I was wondering if this is the class side version of runBenchmark: >> >> Stef >> >> >> On Jun 16, 2013, at 12:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >> >>> I started to read the code (and its self-documentation aspect is not totally there). >>> >>> >>> (SMarkLoops new runOnly: #benchFloatLoop) run >>> >>> Stefan I started to comment the code so are you interested in the commits? >>> >>> >>> Stef >>> >>> >>>> Hi camillo/Stefan >>>> >>>> I would like to know how to use SMark and document it. >>>> Do you have a start of a blog/doc/slide that I can use as a start? >>>> >>>> I'm thinking that I could use the implementation of Trie of Benoit and the one of Cuis >>>> as an example to do some benchs. >>>> Since I'm not fluent in benchmarks, I think that this the occasion to learn. >>>> >>>> Stef

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by Camillo Bruni

#profile: is supposed to open the profiler on the given benchmark. let me fix that :) On 2013-06-16, at 19:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > SMarkLoops profile: #benchArrayAccess > > does not work > > I was wondering if this is the class side version of runBenchmark: > > Stef > > > On Jun 16, 2013, at 12:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> I started to read the code (and its self-documentation aspect is not totally there). >> >> >> (SMarkLoops new runOnly: #benchFloatLoop) run >> >> Stefan I started to comment the code so are you interested in the commits? >> >> >> Stef >> >> >>> Hi camillo/Stefan >>> >>> I would like to know how to use SMark and document it. >>> Do you have a start of a blog/doc/slide that I can use as a start? >>> >>> I'm thinking that I could use the implementation of Trie of Benoit and the one of Cuis >>> as an example to do some benchs. >>> Since I'm not fluent in benchmarks, I think that this the occasion to learn. >>> >>> Stef >>> >>> >> >> > >

June 16, 2013

Re: [Pharo-dev] Package Browser and System Organization

by GOUBIER Thierry

Hi Stephen, I already have such a top-level scheme, but a bit deeper than you describe, with three levels, for Pharo 2.0. It has top-level categories and then it uses a prefix-matching approach (i.e. all configurations goes under Packages>>Configurations). Then, if a package has categories, it will split between categories as an usual browser will do. The goal is to limit each level to a max of ~ 10 / 20 entries at most. It does not require any change to RPackage, PackageInfo and friends (but has to stay synchronized with their API and keep track of system changes such as loading/unloading/creating a package). You can have a look at the code at: https://github.com/ThierryGoubier/AltBrowser Specifically AltBrowser class>>defaultPackageCategoriesNames https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… and AltBrowser class>>getRootItems https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… Where you will see how the system uses the current list of existing packages and the MC/RPackage API. Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Stephen Travis Pope [stephen(a)heaveneverywhere.com] Date d'envoi : samedi 15 juin 2013 21:20 Ã : pharo-dev(a)lists.pharo.org Objet : [Pharo-dev] Package Browser and System Organization Hello Phar-ites! I was at the STIC conference this week, and decided to do a small project in Pharo to "get my feet wet." I ported the "Package Browser" (AKA 6-paned browser) that I prefer to use. the basic idea of it is to parse the system categories into a 2-level hierarchy so that the left-most pane is the top-most packages (Collections, Kernel, System, etc.). If the system is well-organized, this list hardly needs a scroll bar! I'm attaching the code with this letter for your edification. To use the PackageBrowser, it really helps if the system categories form a nice 2-level hierarchy, as in , Collections-Abstract Collections-Arithmetic Collections-Arrayed Graphics-Files Graphics-Fonts Graphics-Primitives etc. The second file below is a system re-org for a Pharo 2.0 image. Obviously this is quite release-dependent, so it would be good to do this once in the release cycle for 3.0. In the "old days," there were about 12 top-level packages -- will this work in Pharo? Enjoy! Stephen Pope (stp) ---- Stephen Travis Pope - stephen(a)FASTLabInc.com<mailto:stephen@FASTLabInc.com> - Santa Barbara, CA

June 16, 2013