Hi Stef:
On 16 Jun 2013, at 12:12, Stéphane Ducasse <stephane.ducasse@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