Should I tune for average query runtime or transactions per second? - dbtuneai/synthetic_workload GitHub Wiki

With DBtune you can tune configuration parameters either to optimize optimize the average query runtime (AQR) or transactions per second (TPS). Note that typically, improving one optimization target will also benefit the other target. However, this choice allows the DBtune optimizer to focus on one optimization objective and provide the best solution for that given optimization target. The three benchmarks we have pre-configured can be tuned both for average query runtime and for transactions per second.

• Choose average query runtime if your workload is composed of complex queries and you wish to reduce the average runtime of one query. The average query runtime can improve even if the machine/workload is not bottlenecked as intensely.
• Choose transactions per second if your machine/workload is hitting a bottleneck and, in other words, an increased workload wouldn't lead to increased overall transactions per second. This option can help you to increase the overall transactions per second of your workload.

For more information on which optimization objective to choose please refer to the "Choose alternative optimization target" section in the user guide.