Performance Test Plan - Sample 1
5 likes•13,605 views
This document outlines a performance test plan for Sakai 2.5.0. It describes the objectives, approach, test types, metrics, goals, tools, and data preparation. The objectives are to validate Sakai meets minimum performance standards and test any new or changed tools. Tests include capacity, consistent load, and single function stress tests. Metrics like response time, CPU utilization, and errors will be measured. Goals include average response time under 2.5s and max under 30s, CPU under 75%, and 500 concurrent users supported. Silk Performer will be used to run tests against a Sakai/Tomcat/Oracle environment. Over 92,000 students and 1,557 instructors of data will be preloaded
Performance Test Plan - Sample 1
- 2. Audit Trail: Date April 2, 2013 April 9, 2013 Version 1.0 1.1 Performance Test Plan Name Atul Atul Comment Initial Revision First round of revisions Page 1
- 3. Table of Contents Reference Documents................................................................................................................................... 3 Objectives and Scope .................................................................................................................................... 3 Exclusions ...................................................................................................................................................... 3 Approach and Execution Strategy................................................................................................................. 3 Load/Stress Test Types and Schedules ......................................................................................................... 3 Test Measurements, Metrics, and Baseline .................................................................................................. 4 Performance/Capability Goals (Expected Results) and Pass/Fail Criteria .................................................... 5 Software and Tools Used .............................................................................................................................. 5 Load Descriptions.......................................................................................................................................... 5 Content and User Data Preparation ............................................................................................................. 6 Load Script Recording ................................................................................................................................... 7 Load Testing Process ..................................................................................................................................... 7 Training Needs .............................................................................................................................................. 7 System-Under-Test (SUT) Environment ........................................................................................................ 7 Test Deliverables ........................................................................................................................................... 8 Team Members and Responsibilities ............................................................................................................ 8 Risk Assessment and Mitigation ................................................................................................................... 8 List of Appendices ......................................................................................................................................... 9 Test Plan Approval ........................................................................................................................................ 9 Performance Test Plan Page 2
- 4. Reference Documents Performance Scalability Goals.xls Objectives and Scope The purpose of this document is to outline the environment and performance test plan for benchmarking Sakai 2.5.0 core tools for use in WileyPLUS E5. In general the purposes of this testing are: Validate the core Sakai framework and certain tools meet the minimum performance standards established for this project. Performance testing any new Sakai tools that are developed Performance testing any changes to Sakai Tools that are planned for WileyPLUS E5 Performance testing any BackOffice applications or integrations Exclusions This test plan will not cover any functional or accuracy testing of the software being tested. This test plan will not cover any browser or software compatibility testing. Approach and Execution Strategy Sakai will be tested using an existing Wiley performance test process. This test plan will serve as the basis for Testware to create Silk Performer Test Scripts. These scripts will be run by Leo Begelman using the Silk Performer software. Unicon, Inc. will watch and measure the CPU utilization of the web and database servers used during testing. Unicon, Inc. will analyze and present the performance test results to Wiley at the conclusion of the performance test cycle. Load/Stress Test Types and Schedules The following tests will be run: Capacity Test – Determines the maximum number of concurrent users that the application server can support under a given configuration while maintaining an acceptable response time and error rate. Consistent Load Test – Long-running stress test that drives a continuous load on the application server for an extended period of time (at least 6 hours). The main purpose of this type of test is to ensure the application can sustain acceptable levels of performance over an extended period of time without exhibiting degradation, such as might be caused by a memory leak. Single Function Stress Test – A test where 100 users perform the same function with no wait times and no ramp up time. This test will help determine how the application reacts to periods of extreme test in a very narrow area of the code. Performance Test Plan Page 3
- 5. Baseline Test – At the conclusion of the Capacity Test and Consistent Load Test a third test will be established with the goal to be a repeatable test that can be performed when any portion of the system is changed. This test will not have the secondary goals the other two tests have, and will simply exist to be a known quantity rather than the breaking point values the other tests are interested in. Test Measurements, Metrics, and Baseline The following metrics will be collected Database Server: CPU Utilization – Max., Avg., and 95th percentile. This data will be collected using the sar system utility. SQL query execution time: The time required to execute the top ten SQL queries involved in a performance test run. This data will be collected using Oracle Stats Pack. Application Server: Application Server CPU – Max., Avg., and 95th percentile. This data will be collected using the sar system utility. Memory footprint: The memory footprint is the peak memory consumed by the application while running. This data will be collected using the Java Virtual Machine (JVM) verbose garbage collection logging. Time to last byte (TTLB): This is what will currently be measured in the stress tests, as opposed to user-perceived response time. Time to last byte measures the time between the request leaving the client machine and the last byte of the response being sent down from the server. This time does not take in to account the scripting engine that must run in the browser, the rendering, and other functions that can cause a user to experience poor performance. If the client-side script is very complex this number and the user perceived response time can be wildly different. A user will not care how fast the response reaches their machine (about the user perceived response time) if they cannot interact with the page for an extended amount of time. This data will be collected using Silk Performer. Network: Network Traffic: Network traffic analysis is one of the most important functions in performance testing. It can help identify unnecessary transmissions, transmissions which are larger than expected, and those that can be improved. We need to watch network traffic to identify the bytes over the wire being transmitted, the response times, and the concurrent connections that are allowed. This data will be collected using the sar system utility. Performance Test Plan Page 4
- 6. Performance/Capability Goals (Expected Results) and Pass/Fail Criteria The following are performance requirements (success criteria) for the performance tests: The average response time (measured by the Time to last byte metric) is less than 2.5 seconds The worst response time (measured by the Time to last byte metric) is less than 30 seconds The average CPU utilization of the database server is less than 75% The average CPU utilization of the application server is less than 75% Each blade server must be capable of handling 500 concurrent users The maximum number of acceptable server errors, non HTTP-200 status codes on client requests, will be less than 2% of all client requests. Software and Tools Used Component Software Version Sakai Sakai 2.5.0 GA Servlet Container Tomcat 5.5.25 Java Virtual Machine Sun Java Development Kit 1.5.0.14 Database Oracle 10g (version 10.?.?.?) Load Test Tool Silk Performer Load Descriptions Each test outlined in section 5 will run with a ratio of 59 students to 1 instructor. There is no expected difference between users logging in for the first time or subsequent logins given how the data (outlined in section 10) will be created. The data set these tests will start with will appear to be in mid-course for all users. There will be no ramp up time for any of the Single Function Stress Tests. The ramp up time for all other tests, should be set to 1 user every 3 seconds. 120 users should therefore be running within 6 minutes. In order to place as much stress on the system as possible with a small number of users, all users should come from different worksites. Performance Test Plan Page 5
- 7. Content and User Data Preparation The Sakai system will need to be preloaded with data before the performance testing will begin. This data will be created using the Sakai Shell and Sakai Web Services. Once the data is created it will be extracted from the database with a database dump. The following table identifies several types of data that will need to be preloaded into the Sakai environment. Type of Data Amount of Data Users 93567 Students 92000 Instructors 1557 Administrators 10 Very Large Worksites 2 Large Worksites 5 Medium Worksites 50 Small Worksites 1500 Students to Instructors Ratio 59 to 1 Students per Very Large Worksite 1000 Students per Large Worksite 500 Students per Medium Worksite 250 Students per Small Worksite 50 Announcements per Worksite 13 Forum Topics per Worksite 1/3 of all forum posts in a worksite Forum Posts per Worksite (spread across topics) ¼ students in worksite * 6.5 Columns (Assignments) in Gradebook 13 Instructor Resource per Worksite 20 Performance Test Plan Page 6
- 8. Load Script Recording Testware will create new Silk Performer Test Scripts based on the two scenarios outlined in Appendices 1 and 2. The Test Suite should be set up to accommodate a ratio of 59 students to 1 instructor. Wait time should be included between each page request, so that the total time for an activity is equal to the number of page requests * 2.5 seconds + the total wait time. Load Testing Process This section details the load testing process that will be followed for all performance tests conducted as described in this test plan. Start data collection scripts Stop the application Remove any temporary files Reset the database and file system to known starting points Start the application and run a quick sanity test to make sure each application server can successfully return login screen markup can successfully process a login request. Request the Silk Performer scripts be started Once the Silk Performer scripts have completed, stop the data collection scripts Acquire any database specific data being collected Collate the data for all the metrics specified into one report. Make the report available in the Wiley Portal Training Needs Testware will need to be trained on the use of the Sakai environment. The scenarios outlined in Appendix 1 and Appendix 2 give some idea about which parts of Sakai will be used, however, more training will probably be required by the Test Script writers. System-Under-Test (SUT) Environment Specifying mixes of system hardware, software, memory, network protocol, bandwidth, etc Network access variables For example, 56K modem, 128K Cable modem, T1, etc. ISP infrastructure variables For example, first tier, second tier, etc. Client baseline configurations Computer variables Browser variables Performance Test Plan Page 7
- 9. Server baseline configurations Computer variables System architecture variables and diagrams Other questions to consider asking: What is the definition of “system”? How many other users are using the same resources on the system under test (SUT)? Are you testing the SUT in its complete, real-world environment (with load balances, replicated database, etc.)? Is the SUT inside or outside the firewall? Is the load coming from the inside or outside of the firewall? Test Deliverables The following test deliverables are expected as part of this performance testing effort. Test Plan – This Document Test Scripts – Silk Performer Test Scripts to implement the scenarios outlined in Appendix 1 and Appendix 2 Test Results Data – The data resulting from the performance tests run Test Results Final Report – The final report that documents and analyzes the results of the performance tests that were conducted according to this test plan. Team Members and Responsibilities The following table defines the different team member responsibilities. Responsibility Team Member Test Plan Creation Atul Silk Performer Test Script Creation TestWare Validation of Test Script Execution Atul Silk Performer Test Script Execution Prerana CPU Monitoring and Test Orchestration Sam Database Loading and Analysis Ramu Risk Assessment and Mitigation Performance Test Plan Page 8
- 10. Business Risk: Unsatisfactory Performance of Sakai Mitigation: Conduct performance testing of core Sakai at the beginning of the project. If Sakai does not meet the goals established above, project management will have the most time possible to adjust project plans. IT Risk: Limit on the number of virtual users available with Silk Performer Mitigation: Test only one blade server per 500 virtual users available with Silk Performer Risk: All Sakai tools needed for testing at this stage may not be available Mitigation: Tests will be conducted against the core tools that are in the Sakai 2.5.0 release. Where a tool that is needed is not yet available, and place holder tool has been specified in the test scenarios in Appendix 1 and 2. (e.g., Calendar will be used in place of Student Gateway for this testing) List of Appendices Appendix 1 – Student test scenario Appendix 2 – Instructor test scenario Appendix 2 – Single function stress test scenarios Test Plan Approval Business Approval __________________________________________________ Paul Harris _____________ Date IT Approval __________________________________________________ Raghav _____________ Date Testing Approval ___________________________________________________ Venkat Performance Test Plan _____________ Date Page 9