TesPlan Run Explorer Performance?

When opening run explorer it is painfully slow and displays “Searching” for a long time. Tagging a run brings “searching” back which seems odd and changing the view to “results” to test limit sets took several minutes. Is this normal behavior? When Launching Results Viewer from Editor, the program starts almost immediately. When trying the same from Run Explorer it’s painful.

1 Like

This is a known issue with using tags as DBs get larger. We are looking at ways to improve this. It does get worse as the DB grows, so if you are able to achieve an SQLite DB and create a new one that will help. Recognized that this is not an ideal solution.