Closed kbrock closed 9 years ago
Come to think of it, it seems like there are a number of similar interfaces here.
the json and comparison interfaces just take data
, though in 2 different formats. summary too for that matter.
the suites and $stdout (called from run / warmup) have similar interfaces as well. not sure if you are curious about making all 5 of these similar.
It seems consolidation of this interface may be beneficial, but keeping them separate works for me too. If you think it may work, just say so and I can throw something together
Quite right, that's a typo.
I think
iter
means thatips
is not available, andruntime
should be used instead.I'd like to write specs around this and wanted to make sure I understood the purpose of
iter
Benchmark::Compare#compare
is called with@entries
byIPS
. It looks like@entries
comes fromadd_entry
, which populatesips
but notruntime
.ips
,ips_sd
ORruntime
?Seems the gem is focused on a) determining the iteration values, b) timing, c) comparing, and d) reporting - but in theory any of those could be swapped out. E.g.: the timing could be from ruby-prof or even an explain plan from psql.
Is this close to your thought path / of interest?
printf
in this method with%20s
rather than theputs
andprintf
mix. Thoughts?