I'm not quite sure about the license of the class in Dolphin. So I'll
make something simple on my own. I basically just need some structured
storage and don't like the three-element Array approach.
Thanks,
Udo
On 12.09.13 23:25, Esteban A. Maringolo wrote:
You can file it in from Dolphin...
we should add that to the book chapter :)
On Sep 14, 2013, at 2:16 PM, Camillo Bruni wrote:
> Short Answer:
> -
> problemSize is used to calibrate your benchmark, so usually you adapt this
> value for
> your machine. And yes you are right, the result is not divided by the
> problem
Thanks, Camillo, for that big and very useful letter. You helped me a lot.
Best regards,
Natalia
14.09.13 15:16, Camillo Bruni написав(ла):
Short Answer:
-
problemSize is used to calibrate your benchmark, so usually you adapt this
value for
your machine. And yes you are right, the re
Short Answer:
-
problemSize is used to calibrate your benchmark, so usually you adapt this
value for
your machine. And yes you are right, the result is not divided by the
problemSize.
Long Answer:
The typical use case is like this:
MathBench >> benchLoopSinus
1
Thanks
13.09.13 12:06, Damien Cassou написав(ла):
On Wed, Sep 11, 2013 at 9:04 PM, Natalia Tymchuk
wrote:
I want to draw a bar diagram for my benchmarks in Graph-ET. Does anybody
know how to add the labels to x-axis?
you may want to ask on the moose mailing list or on stackoverflow (tag #p
Hello.
I have a question about problemSize in benchmarking. I got the small
times from running benchmarks and that's why I try to use problemSize
like in the video http://vimeo.com/68494202. But the benchmark for which
I rewrote code and used problemSize has given me very big result. Maybe
it
Thierry I think that what ben want to say is:
- provide a default
"but I don't want to enforce a specific way of organising the git
repository… "
Stef
PS: I would love to be able to use git for managing Pharo so keep pushing. Now
we cannot allocate more resources to this task b
