Thanks for the post! Closing open test runs helps TestRail by reducing the amount of data which is loaded in ToDo pages and other areas of TestRail.
Additionally, deleting old, unneeded data from TestRail should also help with performance, as this would help reduce the size of TestRail’s database. You can also implement this as part of your automated runs and you can look into purging test runs that are older than a certain threshold (e.g. 2-4 weeks) and closed, for example. The idea for this is to use the
get_runs API method with a
created_before filter and then delete old runs with
delete_run . If you use plans instead, the equivalent would be
I can also recommend reviewing your I/O and database configuration and we do have a general performance optimization guide on our website here:
Please let me know in case you have any further questions, happy to help,