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 <[email protected]> wrote: > there is no ScriptConsole but I imagine that using Transcript is ok. > > On Jun 16, 2013, at 8:45 PM, Stéphane Ducasse <[email protected]> > 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 <[email protected]> >>> 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 >>> >>> >> >
