Hi Tim,

    the below is lovely and makes it easy to run from the command line.  Please can we keep it?  The Mac VM's command line support is broken (but being fixed) so test in Windows using a console VM and/or in Linux.

One more request, it would be great if the package was load able and runnable in VW in some form so that at least one can gather a complete baseline set of results from VW.

_,,,^..^,,,_ (phone)

> On Apr 28, 2016, at 5:19 AM, Stefan Marr <smalltalk at stefan-marr.de> wrote:
> 
> Hi Tim:
> 
>>> On 28 Apr 2016, at 13:01, Tim Felgentreff <timfelgentreff at gmail.com> wrote:
>>> 
>>> - can it be controlled from the command line?
>> 
>> Yes, provided you mean "use a .st file argument". To run a benchmark
>> you can write e.g.
>> - BenchmarkAutosizeSuite run: {'BenchmarkSimpleStatisticsReporter'.
>> 'SMarkShootout'. 100}. # runs all shootout benchmarks for 100 outer
>> iterations, reporting statistics in the autosize suite
>> - BenchmarkCogSuite run: {'BenchmarkSimpleStatisticsReporter'.
>> 'SMarkShootout.benchBinaryTrees'. 100}. # runs the binarytrees
>> benchmarks for 100 outer iterations without autosizing, but with one
>> extra iteration for warmup
> 
> I look at your changes to the code, but if you didn’t remove any SMark features, there is also a proper command-line interface.
> 
> See: http://forum.world.st/Convention-to-build-cmd-line-interfaces-with-Pharo-td3524056.html
> 
> $ squeak-vm.sh Pharo-1.2.image --help 
> SMark Benchmark Framework, version: SMark-StefanMarr.12 
> 
> Usage: <vm+image> SMarkHarness [runner] [reporter] <suiteOrBenchmark> 
>                               [iterations [processes [problemSize]]] 
> 
> Arguments: 
> runner             optional, a SMarkRunner class that executes the benchmarks 
> reporter           optional, a SMarkReporter class that processes 
>                              and displays the results 
> suiteOrBenchmark   required, either a SMarkSuite with benchmarks, 
>                              or a benchmark denoted by Suite.benchName 
> iterations         optional, number of times the benchmarks are repeated 
> processes          optional, number of processes/threads used by the benchmarks 
> problemSize        optional, depending on benchmark for instance number of 
>                              inner iterations or size of used data set 
> 
> 
> Best regards
> Stefan
> 
> -- 
> Stefan Marr
> Johannes Kepler Universität Linz
> http://stefan-marr.de/research/
> 
> 
> 
>