Bug 1025669

Summary:	[Performance][TestRun] It is too slow(waiting for more than 3 mins) when create a run or update a case in a run.
Product:	[Other] TCMS	Reporter:	Chen Chen <chechen>
Component:	Usability	Assignee:	cqi
Status:	VERIFIED ---	QA Contact:	Nobody <nobody>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.8.5	CC:	atodorov, cqi, jcai, junzhang, jzhao, leiwang, ryang, xkuang, yuwang
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Chen Chen 2013-11-01 08:47:42 UTC

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)

How reproducible:
100%

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.

Actual results:
1.Run is created after waiting for more than 3 mins.
2.Case is updated after waiting for more than 3 mins.

Expected results:
1.Run is created quickly.
2.Case is updated quickly.

Additional info:

Comment 1 Chen Chen 2013-11-05 07:56:12 UTC

Additional info:
View in another browser tab, in fact, that run is created/updated in the server, just the client has no response.

Comment 3 yangqiu 2014-04-04 03:36:16 UTC

https://projects.engineering.redhat.com/browse/TCMS-177
https://projects.engineering.redhat.com/browse/TCMS-186

Comment 4 Alexander Todorov 2014-04-04 12:34:37 UTC

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.

Comment 5 Alexander Todorov 2014-04-04 12:52:20 UTC

Update: 

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.

Comment 6 Tingting Zhao 2014-10-24 09:04:12 UTC

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.