Open GoogleCodeExporter opened 9 years ago
So, I think there are a few things that I can pull out of this report:
1) dryRun has always been a simple invocation of the benchmark method. Thus
far we've been pretty happy with that. Applying a timeout would at least
require a different thread. I'm not entirely opposed to that, but I'm not sure
that skipping a "dry run" is really in the spirit of a "dry run".
2) Adding meaning to negative values of time limit seems odd to me. If we were
to put some sort of time limit specifically on dry runs, I don't think that
we'd overload the time limit for that.
3) It sounds like there are times where you just want to run a subset of your
parameters. Dry runs seem orthogonal to which algorithms you select. Can you
just use the -D flag or the -b flag to select the correct experiments?
4) I think that adding messaging about dry runs specifically to the console
output is a good idea. At least then you would be aware that dry runs are
happening.
Original comment by gak@google.com
on 8 Jul 2013 at 5:45
Original issue reported on code.google.com by
erich.sc...@gmail.com
on 7 Jul 2013 at 11:01