Bug 1028945 - [Performance] Creating large test run respond more than 5 seconds
Summary: [Performance] Creating large test run respond more than 5 seconds
Keywords:
Status: NEW
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: Devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: cqi
QA Contact: Nobody
URL:
Whiteboard:
: 905720 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-11 10:01 UTC by Xiong Zhi Ming
Modified: 2022-03-14 03:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Xiong Zhi Ming 2013-11-11 10:01:07 UTC 
Description of problem:
Select about 1000 test cases and create a test run, WriteTestRun and SaveTestRun respond more than 5 seconds.

Version-Release number of selected component (if applicable):
V3.8.5

How reproducible:
100%

Steps to Reproduce:
1. Open a test plan which testcases number is about 1000 (such plan id is6578)
2. select all test cases then create a new test run
3.

Actual results:
Page Name       Elapse Time(ms)
WriteTestRun	8012
SaveTestRun	14597
OpenTestRun	4921

Expected results:
All pages response time are less than 5 seconds.

Additional info:
Test env:
Server	Function	OS	CPU	Memory	Software
dhcp-8-146.nay.redhat.com	DB Server	Red Hat Enterprise Linux Server release 6.3	1 CPU (4 Cores)	4G	MySQL 5.1.67
tcms-test.app.eng.nay.redhat.com	Web Server	Red Hat Enterprise Linux Server release 5.1	2VCPU	2GB	"Apache Http Server 2.2
Nitrate 3.8.5"
dhcp-8-145.nay.redhat.com	JMeter load generator	Red Hat Enterprise Linux Server release 6.3	1 CPU (8 Cores)	8G	JMeter 2.9
Comment 1 Xiong Zhi Ming 2013-11-12 03:02:42 UTC 
*** Bug 905720 has been marked as a duplicate of this bug. ***
Comment 2 Tingting Zhao 2014-10-22 05:44:32 UTC 
verify on qa server with 3.8.11-1
when create or clone a new run with 756 cases,the CPU usage is up to 94% ,and responds about 15 seconds.
Note You need to log in before you can comment on or make changes to this bug.