Red Hat Bugzilla – Bug 1025669
[Performance][TestRun] It is too slow(waiting for more than 3 mins) when create a run or update a case in a run.
Last modified: 2016-05-26 09:17:55 EDT
Description of problem:
It is too slow(waiting for more than 3 mins) when create a run or update a case in a run.
Version-Release number of selected component (if applicable):
3.8.5 on dev server(https://tcms.qe.lab.eng.nay.redhat.com)
Steps to Reproduce:
1.Enter into a plan, click "Cases" label, choose only one case, Click "Write new run" label below the "Run" label.
2.Enter into a run in which there are cases being updated, choose one updated case, click 'Cases'->'Update' menu at the top of the cases list.
1.Run is created after waiting for more than 3 mins.
2.Case is updated after waiting for more than 3 mins.
1.Run is created quickly.
2.Case is updated quickly.
View in another browser tab, in fact, that run is created/updated in the server, just the client has no response.
Same slowness when cloning a previous test run into a new one. For me it usually happens when I clone 2 runs (in 2 tabs). The first one clones and redirects the browser immediately, while the second one waits for quite some time.
although the new test run is visible from the main page it doesn't contain all test cases. Couple of minutes after the clone, and while the original tab was still waiting to be refreshed I opened the new test run into a new tab. It contained only 3 (out of 10) test cases at that moment.
After writing the above comment I refreshed the tab and now it contains 5 of 10 cases.
It looks like TCMS is running a loop over the items which need to be cloned and cloning them one by one.
Raising Prio/Sev because this negatively impacts QE workflow and productivity. Also a regression b/c it has never been so slow previously.
verify on qa server with nitrate 3.8.11:
the response time when creating run or updating cases is less than 3 minus,just about 3 seconds.