Content

• Load testing Report
• Load testing Report
• Introduction
• Install
• Prerequisites
• Elements of a Minimal Test Plan
• Test Plan
• Collection of API
  • List of API
  • Load the JMeter Script
• Make jtl File
• Make html File
• HTML Report

Load testing Report

Concurrent Request	Loop Count	Avg TPS for Total Samples	Error Rate	Total Concurrent API request
200	1	2.7	0%	1000
300	1	4.4	0%	1500
400	1	8	0.35%	2000

Summary

• While executed 400 concurrent request, found 7 request got connection timeout and error rate is 0.35%.
• Server can handle almost concurrent 300 API call with almost zero (0) error rate.

Introduction

This document explains how to run a performance test with JMeter against an simplelearn.com.

Install

Java
https://www.oracle.com/java/technologies/downloads/

JMeter
https://jmeter.apache.org/download_jmeter.cgi

Click =>Binaries
=>apache-jmeter-5.6.2.zip

We use BlazeMeter to generate JMX files
https://chrome.google.com/webstore/detail/blazemeter-the-continuous/mbopgmdnpcbohhpnfglgohlbhfongabi?hl=en

Prerequisites

• As of JMeter 5.6, Java 8 and above are supported.
• we suggest multicore cpus with 4 or more cores.
• Memory 16GB RAM is a good value.

Elements of a minimal test plan

• Thread Group

  The root element of every test plan. Simulates the (concurrent) users and then run all requests. Each thread simulates a single user.

• HTTP Request Default (Configuration Element)

• HTTP Request (Sampler)

• Summary Report (Listener)

Test Plan

Testplan > Add > Threads (Users) > Thread Group (this might vary dependent on the jMeter version you are using)

• Name: Users

• Number of Threads (users): 200 to 400

• Ramp-Up Period (in seconds): 1

• Loop Count: 1

  1. The general setting for the tests execution, such as whether Thread Groups will run simultaneously or sequentially, is specified in the item called Test Plan.

  2. All HTTP Requests will use some default settings from the HTTP Request, such as the Server IP, Port Number, and Content-Encoding.

  3. Each Thread Group specifies how the HTTP Requests should be carried out. To determine how many concurrent "users" will be simulated, one must first know the number of threads. The number of actions each "user" will perform is determined by the loop count.

  4. The HTTP Header Manager, which allows you to provide the Request Headers that will be utilized by the upcoming HTTP Requests, is the first item in Thread Groups.

Collection of API

• Run BlazeMeter

• Collect Frequently used API

• Save JMX file then paste => apache-jmeter-5.6.2\bin

  List of API

  • https://www.simplilearn.com/
  • https://www.simplilearn.com/resources
  • https://www.simplilearn.com/business
  • https://www.simplilearn.com/become-our-trainer
  • https://www.simplilearn.com/reseller-partner-program-for-training-courses

  OR

  Load the JMeter Script

  • File > Open (CTRL + O)
  • Locate the "simpleLearn_u200.jmx" file contained on this repo
  • Continue open simpleLearn_u200.jmx to simpleLearn_u400.jmx
  • Open those file
  • The Test Plan will be loaded

Test execution (from the Terminal)

• JMeter should be initialized in non-GUI mode.
• Make a report folder in the bin folder.
• Run Command in jmeter\bin folder.

Make jtl file

  jmeter -n -t  simpleLearn_u200.jmx -l simpleLearn_u200.jtl

Then continue to upgrade Threads(200 to 400) by keeping Ramp-up Same.

After completing this command

Make html file

jmeter -g report\simpleLearn_u200.jtl -o simpleLearn_u200.html

• g: jtl results file

• o: path to output folder

• 
  

HTML Report

Number of Threads 200 ; Ramp-Up Period 1s

Requests Summary	Errors

Number of Threads 300 ; Ramp-Up Period 11s

Requests Summary	Errors

Number of Threads 400 ; Ramp-Up Period 1s

Requests Summary	Errors