How to benchmark your PrestaShop Shop (Front-office)

Follow instruction on Back-Office benchmark page to get a pre-populated shop and to run Gatling scenarios on it.

PrestaShop performance project on Github includes Front-Office scenarios you can edit to get your own scenarios running.

Benchmark with Siege tool

Benchmark methodology

In order to benchmark the performances of your shop, you will use the siege testing tool. Try to always use the latest available version HERE.

Setup siege configuration

Create a txt file url.txt with various urls from your shop: (prepend with the domain of your shop)


Run the siege benchmark

Then run a siege benchmark using this file:

siege -b -i -c 1 -t 20S --no-parser -f url.txt

We will first warmup the cache by testing 1 time with 1 concurrent user, and then progressively raise the number of concurrent users until the performances actually decreases.

Raise the concurrent parameter (-c 1) to the number of concurrent users you want to test.

Ex for 10 concurrent users without MySQL query cache:

siege -b -i -c 10 -t 20S --no-parser -f url.txt  

Lifting the server siege...
Transactions:		         879 hits
Availability:		      100.00 %
Elapsed time:		       19.26 secs
Data transferred:	       37.32 MB
Response time:		        0.22 secs
Transaction rate:	       45.64 trans/sec
Throughput:		        1.94 MB/sec
Concurrency:		        9.92
Successful transactions:         879
Failed transactions:	           0
Longest transaction:	        0.68
Shortest transaction:	        0.03

With MySQL query cache enabled:

Lifting the server siege...
Transactions:		        1114 hits
Availability:		      100.00 %
Elapsed time:		       19.46 secs
Data transferred:	       46.70 MB
Response time:		        0.17 secs
Transaction rate:	       57.25 trans/sec
Throughput:		        2.40 MB/sec
Concurrency:		        9.93
Successful transactions:        1114
Failed transactions:	           0
Longest transaction:	        0.57
Shortest transaction:	        0.02

Interpret the results

In the siege result output, here is the useful results:


The total number of pages loaded during the benchmark. The higher the better.


It tells you the amount of pages which have failed to load.

Response time

The average response time of your pages. The lower the better.

Transaction rate

The number of pages loaded by second. The higher the better.


The number of concurrent transaction the software has been able to run. Should be close to the requested concurrent user setting.

Failed transactions

Closely related to Availability, the number of pages which have failed to load (404, 503, …)