Use "Architect" tool to partition the testresult table
https://architect.readthedocs.io/index.html
Right now, the testresult table is bloated and gigantic. This leads to lower performance and poor access time due to data not being consecutive in memory.
To address this, we should partition the table by runconfig name, so as deleting a run does not introduce any fragmentation and compressing a run would reclaim the disk space used quickly (thanks to vacuum full).
The big unknown is the performance impact when running long queries, but I honestly can't tell if it is going to be much faster due to the defragmentation, or much slower due to bad query planning.