Gain insights into Gatling fundamentals, delve into advanced scripting, simulate network conditions with puppeteer and lighthouse, and set up Jenkins CI for scalable performance testing automation.

performance.tar.gz

Puppeteer

Gatling-1

Java

shell

Lighthouse

gatling-spa-run-framework

gatling-spa-run-framework-copy

Gatling

gatling-local-server

gatling-local-server-live

Almost every company in the world needs to test its scalability and performance of their products or applications.

In this course, you will learn the fundamentals of Gatling, an open-source performance testing tool that is in great demand in the software industry. You will start by learning the basics of performance testing including scalability testing and stress testing.

You will then move on to more advanced concepts such as writing Gatling scripts, understanding web page performance and simulating network throttling using puppeteer and lighthouse tools.

Lastly, you will learn to set up Continuous Integration (CI) using Jenkins for Gatling which will be useful for running tests remotely. By the end of this course, you will have some new great skills for your resume.

Performance Test Automation 101: Gatling, Lighthouse, & Jenkins

There are various key metrics that we use to evaluate the performance of a system. These are:



#### **CPU and memory usage**
When the load increases, the server would need more computing power in terms of memory and CPU to scale. This can be achieved using *vertical* or *horizontal* scaling.

> **Vertical scaling:** This occurs when we increase the computing power of the server by adding more resources (CPU, RAM) so that the application can handle an increased load.

> **Horizontal scaling:** This occurs when we increase the number of servers so that the application can handle the increased load.

#### **Network bandwidth**

This is the measure of the maximum amount of data that can be transferred per unit of time through the given network.

Let's say we have a network bandwidth of 128**kbps**, which means 128kb of maximum data can flow through the network per sec.

> **kbps** -- *kilobits* per sec

#### **Throughput**

Throughput is the measure of the amount of data transferred at a given time. In other words, throughput is the number of requests a software system can process successfully per time unit (per sec or per hour or per minute).

Let's look at an example. If a packet with a size of 10 *bytes* takes 1 second to flow from system A to the system B, we can say the throughput between the two systems is 80*bits per sec* (80bps ~ 0.08**kbps**).

> 1 byte = 8 bits

> **"Difference between throughput and network bandwidth":** Throughput is the actual measurement of how much data is successfully transferred through the network, whereas network bandwidth is a theoretical measurement. *Throughput* will always be **less** than *network bandwidth*.


#### **Latency and response time**

This is the time taken for a client to get the server response once a request was sent. It is also known as ‘Network Delay’.

* The client sends a request at time=0.
* The request reaches the server in **2 seconds** at time=2.
* The server takes 1 second to process (time= 3)
* The response reaches the client in **2.1 seconds** (time=5.1)

*The network latency* = 2+1+2.1 = **5.1 seconds**.






# **CPU and memory usage**
When the load increases, the server would need more computing power in terms of memory and CPU to scale. This can be achieved using *vertical* or *horizontal* scaling.

> **Vertical scaling:** This occurs when we increase the computing power of the server by adding more resources (CPU, RAM) so that the application can handle an increased load.

> **Horizontal scaling:** This occurs when we increase the number of servers so that the application can handle the increased load.

# **Network bandwidth**

This is the measure of the maximum amount of data that can be transferred per unit of time through the given network.

Let's say we have a network bandwidth of 128**kbps**, which means 128kb of maximum data can flow through the network per sec.

> **kbps** -- *kilobits* per sec

# **Throughput**

Throughput is the measure of the amount of data transferred at a given time. In other words, throughput is the number of requests a software system can process successfully per time unit (per sec or per hour or per minute).

Let's look at an example. If a packet with a size of 10 *bytes* takes 1 second to flow from system A to the system B, we can say the throughput between the two systems is 80*bits per sec* (80bps ~ 0.08**kbps**).

> 1 byte = 8 bits

> **"Difference between throughput and network bandwidth":** Throughput is the actual measurement of how much data is successfully transferred through the network, whereas network bandwidth is a theoretical measurement. *Throughput* will always be **less** than *network bandwidth*.


# **Latency and response time**

This is the time taken for a client to get the server response once a request was sent. It is also known as ‘Network Delay’.

* The client sends a request at time=0.
* The request reaches the server in **2 seconds** at time=2.
* The server takes 1 second to process (time= 3)
* The response reaches the client in **2.1 seconds** (time=5.1)

*The network latency* = 2+1+2.1 = **5.1 seconds**.






Learn about the key metrics that help us monitor or identify system performance issues.

Introduction

Basics of Performance Testing

Gatling: Load and Stress Testing Tool

Gatling: Script Features

Examples: Simulations Using Gatling

Web Page Performance

Network Throttling

Download Custom Gatling Test Framework

Gatling with Jenkins

Conclusion

Key Performance Metrics

CPU and memory usage