[darcs-devel] [issue1690] Create benchmark for darcs 2.4 announcement

[Eric Kow]

Eric Kow <kowey at darcs.net> added the comment:

The right answer in these kinds of situations is (almost) always to
automate.  

We could conceivably extend darcs-benchmark report with a gnuplot option
(hopefully re-using as much pre-existing code as possible).  The bad
news is that this would mean impinging on our volunteers for another
round of benchmarking.  The good news is that the upcoming version of
darcs-benchmark now saves results, so if we do ask them for more work,
it should be the last time we'll need their computers to be crunching
away.  I'm hoping that the plan of making it really easy for benchmarks
to accumulate works out.  Moar data!

[NB. I may not be able to work on the visualisation aspect of
darcs-benchmark until Sunday if at all, and it's looking like my
endurance is starting to thin out.  So no promises!  Better send in
those patches :-)]

----------
status: unknown -> need-implementation

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue1690>
__________________________________