| Add an initial tool (say ext/bin/check-query-perf or something) to run a query performance test (for now just capturing query execution times) against puppetdb, likely via ./pdb, when given a set of queries and the pdb address (or could just default to localhost:8080 for now). It's fine for it to be a requirement that lein uberjar has already been run. One place we might consider storing the queries, if they're not sensitive, is somewhere in dev-resources/. It's completely fine for the first implementation to be as simple as (effectively) running time curl ... -d@query-file > /dev/null once for each query and saving the times somewhere for later processing.
We'll probably also eventually want some way, perhaps via gnuplot, or matplotlib to quickly compare results, but that can be addressed separately. Capturing the execution times, can support that work, and future possible automated regression testing. While we don't need (and might not want for now) the full automatic PDBBOX creation whenever one isn't already indicated in the environment that ext/bin/render-pdb-schema does, we might want to follow some of the existing argument conventions/behaviors there and in our other tools. For example, if we want to allow specification of the pdb to query, we could use --pgport PGPORT, etc. |
