Warning: You are browsing the documentation for PrestaShop 1.7, which is outdated.
You might want to read an updated version of this page for the current version, PrestaShop 8. Read the updated version of this page
In order to benchmark the performances of the backoffice of your shop, you will use the Gatling testing tool.
Note: Backoffice benchmark is only possible starting with PrestaShop 220.127.116.11!
If you want still want to run the test for version < 18.104.22.168, take a look at this PR: https://github.com/PrestaShop/PrestaShop/pull/8876
Gatling is a stress tool. Development is currently focusing on HTTP support. We won’t explain here the fundamentals of Gatling, but for more details I suggest you to have a look at the Gatling project.
To follow these instructions, you will use the following github repository: PrestaShop performance project
git clone [email protected]:PrestaShop/performance-project.git
Benchmarks require a pre-populated shop. But this shop content has to be the same at each new bench in order to get reproducible results. PrestaShop ShopCreator project will help to generate fixtures, used during shop installation to populate the benched shop.
cd performance-project cd shop
README.md contains instructions to get a working shop filled with fixtures, using “PrestaShop ShopCreator” project
git clone [email protected]:PrestaShop/prestashop-shop-creator.git
ShopCreator requires a config file to know which fixtures it has to generate. shop-creator-config.yml is the one used in this study. You can customize it to fit your own needs. Copy it in the ShopCreator /config/ directory.
cp shop-creator-config.yml prestashop-shop-creator/app/config/
First we need to install required ShopCreator dependencies
Once your config is ready, run fixture generation in ShopCreator directory
Fixtures are created in /generated_data/ directory. It contains xml files with data for each PrestaShop entity, and images for products, categories…
To use these generated fixtures, you need to copy the directory content into the installation directory of PrestaShop before installing the shop
cp -R generated_data/* [prestashop]/install/fixtures/fashion/
Make sure you’re not in debug mode! In config/defines.inc.php you should have:
Once this is done, simply install and run your shop. If you want to use our pre-configured Dockerfile to do this, just keep reading.
The directory /prestashop-performance/ contains required Dockerfile and scripts to install and run a shop with generated fixtures
Copy the previously generated fixtures in the corresponding directory.
cp -R prestashop-shop-creator/generated_data/* prestashop-performance/fixtures/
Then you can build the docker image. This one will embed generated fixtures since the Dockerfile copy them in the image.
cd prestashop-performance docker build -t prestashop-bench .
Your image is ready to use.
Run the shop with the following command:
docker run \ -e FIXTURE_FOLDER=fixtures\ -e PS_DOMAIN=localhost:8080\ -e PS_FOLDER_ADMIN=admin1234\ -e PS_ERASE_DB=1 \ -e PS_CANONICAL_REDIRECT_DISABLE=1 \ -e DB_SERVER=host.docker.internal\ -e DB_PORT=3306\ -e DB_NAME=prestashop_bench \ -e DB_USER=prestashop_bench \ -e DB_PASSWD=prestashop_bench \ -p 8080:80 \ prestashop-bench
Installation can take several minutes, depending on the size of fixtures you set, and of course depending on the machine you run it on.
Once it is done, you should access this shop from http://localhost:8080 on your browser.
The docker image above is used for this study purposes. It is deployed on several stacks detailed in Results. Docker usage makes it easy to customize prestashop installation, or hosting configuration like php tuning, or mysql tuning.
cd performance-project cd benchmark/gatling
Official gatling image needs to be lightly customized. More precisely we need to pass some java arguments to the scenarios.
docker build -t prestashop-bench-gatling .
Provided Gatling run command accepts arguments such as user count, customer count, test duration.
docker run -it --rm \ -v $dir/results:/opt/gatling/results \ -e JAVA_OPTS="-DusersCount=500 -DcustomersCount=20 -DadminsCount=0 -DrampDurationInSeconds=900 -DhttpBaseUrlFO=http://shop2.stack1.prestashop.net -DhttpBaseUrlBO=http://shop2.stack1.prestashop.net/ps-admin [email protected] -DadminPassword=prestashop" \ --add-host=sandbox.prestashop.com:192.168.0.4 \ prestashop/performance-gatling \ -s LoadSimulation
In the example above:
A more scriptable approach could be using the provided
run.sh script. This script aims to properly rename result directory to a more readable one, and process these results to extract some useful data such as the needed “order-per-hour” KPI.
You could then write your own
batch.sh to run multiple gatling benchmarks.
Once unzipping the folder it will look like as shown below:
Now let’s test if our Gatling works well, so you can launch a sample test included natively in the project with the CLI:
And choose the simulation you want to run
In my example I run “ basic.BasicExempleSimulation”
After few minutes you can consult the detailed report generated automatically into “results” folder.
Download the script “parcoursbackoffice.scala” and put it under “/gatling/user-files/simulations”.
Open with your editor the parcoursbackoffice.scala file and setup your script:
To avoid handling the multiple generated token on each back-office page, you can just disable it by following the steps below:
Setup environnement TOKEN variable to “disabled” allows you to disable token in urls for Symfony pages and in legacy pages. If you want to test it you need to setup environment variable (SetEnv TOKEN disabled in Apache vhost configuration file) and check that Symfony pages (Product, Module, …) urls doesn’t contains _token anymore and legacy pages shouldn’t contains token parameter.
For example if you site is setup in /etc/apache2/sites-enabled/000-default.conf
add the value
SetEnv _TOKEN_ disabled
< /VirtualHost >
Note: don’t forget to restart your apache service! Now the token are disabled on your PrestaShop site Back-office, this mean that everyone who can log-in your Back-office could access to anypage from the url page. That why we recommend you to run the benchmark on a website only dedicated to test. If this is not the case, don’t forget to restore it when you finish your performance test.