Load Test Report

How to draft a Load Test Report? An easy way to start completing your document is to download this Load Test Report template now!

Every day brings new projects, emails, documents, and task lists, and often it is not that different from the work you have done before. Many of our day-to-day tasks are similar to something we have done before. Don't reinvent the wheel every time you start to work on something new!

Instead, we provide this standardized Load Test Report template with text and formatting as a starting point to help professionalize the way you are working. Our private, business and legal document templates are regularly screened by professionals. If time or quality is of the essence, this ready-made template can help you to save time and to focus on the topics that really matter!

Using this document template guarantees you will save time, cost and efforts! It comes in Microsoft Office format, is ready to be tailored to your personal needs. Completing your document has never been easier!

Download this Load Test Report template now for your own benefit!

GCOPTS="-99:+UseParallelGC Xloggc:/opt/covalent/ers31/servers/sakai/logs/gc.log -verbose:gc 99:+PrintGCTimeStamps -99:+PrintGCDetails -99:+UseParallelOldGC" JAVAOPTS="-server -Xms2048m -Xmx2048m -99:NewSize=1024m 99:MaxNewSize=1024m -server -99:PermSize=256m -99:MaxPermSize=256m 99:+JavaMonitorsInStackTrace -99:ThreadStackSize=256 GCOPTS" - New Logins / Returning Logins While debugging the performance test environment, one theory we proposed, was maybe there was a difference between new user login and returning user logins.. The Jira issue numbers and titles are: SAK-13188 SAK-11463 Messages Forums Synoptic Tool / More performance improvements Slow queries from Forums Memory Leak While we were performing the massive login/logout test to support returning logins (see previous section “New Logins / Returning Logins”) we discovered that Sakai was running out of memory.. Percent CPU Usage 90.00 80.00 70.00 DB Ave CPU Percent ( ) 60.00 DB Max CPU 50.00 DB 95th CPU App Ave CPU 40.00 App Max CPU 30.00 App 95th CPU 20.00 10.00 0.00 Test ID 03 Test ID 04 Test ID 05 Test ID 06 Test ID 07 Test ID 08 Test ID 09 Test ID 10 Test ID 11 Test ID 12 Test ID 13 Te st ID The graph shows us a couple of interesting things.. Response Times 1 User 20.00 18.00 16.00 14.00 12.00 10.00 8.00 6.00 4.00 2.00 0.00 30 Users 60 Users 120 Users 180 Users 240 Users 300 Users 360 Users 420 Users le s pl oa d ce m un es ct o st ru ub rS In st ru ct o In m it An rU no tS el ec tR en St ud 480 Users Fi en t rc e ou Ad l ic k tC en St ud St ud en tS av e Ev en d t Time (seconds) 15 Users Activity The graph shows us the response times do not appear to dramatically increase as the number of concurrent users is increased.. The number of AJP processors can be set by changing the maxProcessors value in the tomcat.home /conf/server.xml file: Connector port="8009" minProcessors="5" maxProcessors="500" acceptCount="100" enableLookups="false" redirectPort="8443" debug="0" connectionTimeout="800000" protocol="A

DISCLAIMER
Nothing on this site shall be considered legal advice and no attorney-client relationship is established.

Download Load Test Report

Best Calendar Templates

Related templates

Latest templates

Latest topics