The query benchmark currently stores all query responses in the output. basic-query and random-query do not.
For basic and random, it'd be nice to be able to see what queries were actually generated (optionally). As well as what the results of those queries were (also optionally - there may be a lot).
For the query benchmark, it'd be nice to be able to turn off the storing of responses.
The biggest open question is probably where to store the generated queries - one could either add a new field to the bench.Result object which is probably a reasonable thing to do, or put them into the result.Extra map.
The
query
benchmark currently stores all query responses in the output.basic-query
andrandom-query
do not.For basic and random, it'd be nice to be able to see what queries were actually generated (optionally). As well as what the results of those queries were (also optionally - there may be a lot).
For the query benchmark, it'd be nice to be able to turn off the storing of responses.
The biggest open question is probably where to store the generated queries - one could either add a new field to the
bench.Result
object which is probably a reasonable thing to do, or put them into theresult.Extra
map.