Load testing WordPress on cheapest cloud hosting plan

Nowadays the most of the cloud hosting companies are offering 5$ per month hosting plan, we wanted to know if this plan can be used in production and how much load it can handle. This article will include information about how much load can handle WordPress on the cheapest cloud hosting plan. We will reveal if the cheapest cloud hosting plan is marketing thing or it can solve some sort of problems for new starters.

Server set up and WordPress installation

For this load test, we won’t use any server-side nor web app optimizations. We will use cloud hosting built-in features such as “One-click apps” which deploys LEMP or LAMP Stack plus WordPress in one click. With few mouse clicks, we have the cloud server with WordPress installed. We choose LEMP Stack (Linux, Nginx, MySQL and PHP-FPM). Here are hardware properties:


$sudo lscpu

Architecture:          x86_64

CPU(s):                1

Thread(s) per core:    1

Core(s) per socket:    1

Socket(s):             1

CPU family:            6

Stepping:              2

CPU MHz:               1799.998

BogoMIPS:              3599.99

Virtualization:        VT-x

Hypervisor vendor:     KVM

Virtualization type:   full

L1d cache:             32K

L1i cache:             32K

L2 cache:              256K

L3 cache:              30720K

Continue reading “Load testing WordPress on cheapest cloud hosting plan”


Debugging JMeter with Wireshark

In this post, we consider the situation when JMeter request which was recorded with “HTTP(S) Test Script Recorder” does not work but if you repeat steps with browser everything works fine and if you have already tried to debug JMeter script but with no results. In more detail, you recorded HTTP request which should check some sort of API action but when run JMeter script occurring error. API, in turn, didn’t return accurate information about the error. If you try to repeat the steps using a browser then everything works fine. The first thing that may come to mind it so HTTP Cookie Manager, but if after adding HTTP Cookie Manager error persists then have to use Wireshark to see what is wrong. So, open Wireshark, select the network interface if you do not know what interface to choose, choose “any”.


Now run sniffing and write in the box Filter:

http.request.method == "DELETE"

Instead of “DELETE” you can assign “GET”, “POST”, “PUT” according to the method.


After that, open the browser and perform the steps that we need, if the connection between the browser and the server is encrypted you’ll have to decrypt Wireshark packets, but if not then you will see the requests sent. Now you need to save them in a text format, for this select “File” -> “Export” -> “as ‘Plain Text’ file …”. In the new window, select “All expanded”, “Displayed”, insert the name of the file. After that, we need to repeat the previous steps, but only need to capture requests through JMeter. After that, you will have two files with captured packets. Now run or install program Meld:

sudo apt-get install meld

Open the program and select two captured files to compare them.


screenshot_535After analyzing two files figured out that there was no “Content-Type” header in request and this was causing problem. Adding “Content-Type” header solved the problem. That’s it!


Interested in our services? Get a free quote! Contact us!