Description of problem: 11 pages' average response time exceed TCMS performance testing goal Version-Release number of selected component (if applicable): How reproducible: Executing TCMS 100% workload performance testing Steps to Reproduce: 1. Start XML-RPC test, throughput: 4.44 requests/second 2. Set max number of total threads 50, ramp-up period 5 min and duration 1 hour. Workload distribution as following: Test Case(User Scenario) Mix Workload % Peak Hour Visitors Open a Case Run ID 24.99% 13 Change Case Run status 14.65% 7 Case Run filter 3.42% 2 Run report 2.04% 1 Review a Case 4.17% 2 Edit case 6.39% 3 Write new case 3.13% 1 Open a Case summary from plan 8.06% 4 Open a Case from Plan 12.91% 7 Open a Run from plan 7.29% 4 Create a new Run 3.72% 2 Search 6.12% 3 Report 1.43% 1 Total 100.00% 50 3. Execute the test plan we recorded before, monitoring web/app Server and database server hardware resources Actual results: Tested Features Page/Transaction Average Response Mark Time(ms) --------------- ---------------- ----------------------- ---- TestRun Report RunReport 169918 Report OR_Version 25058 TR_GenerateReport 16915 Baseline Test (byTester) CreateTestRun FilterTestRun 12597 WriteTestRun 12573 SaveTestRun 61254 Open Test Plan OpenTestPlan 25641 ReviewTestCase OpenTestRun 7533 OpenReviewingCase 11354 ChangeTestCaseStatus 12194 WriteTestCase NewTestCase 12573 Expected results: Tested Features Page/Transaction Average Response Time(ms) --------------- ---------------- ----------------------- TestRun Report RunReport <=15 Report OR_Version <=15 TR_GenerateReport (byTester) <=15 CreateTestRun FilterTestRun <=5 WriteTestRun <=5 SaveTestRun <=5 Open Test Plan OpenTestPlan <=5 ReviewTestCase OpenTestRun <=5 OpenReviewingCase <=5 ChangeTestCaseStatus <=5 WriteTestCase NewTestCase <=5 Additional info:
thanks for detail pages's average response time which is really help tcms-dev to improve out performance.
> Expected results: > Tested Features Page/Transaction Average Response > Time(ms) > --------------- ---------------- ----------------------- Change the expected result unit to 'Time(s) '
In order to classify and be more convenient to fix, this bug was splited into 3 bugs(1028945,1029262,1029267) *** This bug has been marked as a duplicate of bug 1028945 ***