![]() By handling we mean the number of completed checkouts and the speed of the (add to cart and place order) requests completion by the server.įor example, we can see that the 2 vCPUs / 4GB RAM completes only 104 out of 150 checkouts (in 150/300 test), with average speed of 13670ms for add to cart requests, and 49081ms for place order. Results AnalysisĪs expected, the results show that more powerful servers can handle higher loads. The number of threads is the number of tests that you want to run, and the ramp-up period is the period in which all the tests must be started.įor example, if our test is 150/300, ie 150 number of threads and 300 seconds ramp up period, it means that all 150 tests (where a test is the sequence of – go to the category page, add product #1 to the cart and so on) must start within 300 seconds.Īnother way of looking at 150/300 test is as “1 purchase session every 2 seconds”, ie every 2 seconds we have a customer coming to perform a purchase in our website. The load of the tests is defined by the two parameters – the “Number of Threads” and the “Ramp-up Period”. Understanding the “Number of Threads” and the “Ramp-up Period” Number of failed checkouts, out of number of checkouts We used droplets with the following specs: We used 3 Digital Ocean droplets (servers) to perform our tests. Send payment information and place the order.Send checkout address & shipping information.The test performed the following actions: Therefore, we run our Jmeter test on different combinations of the following factors – server capabilities, the “Ramp-up Period” and “Number of Threads”. In our benchmark we wanted to check how many concurrent buying customers can servers with different capabilities handle within specific period of time. ![]() After recording the test, the Jmeter lets you run it and choose the load of your test (the “Ramp-up Period” and “Number of Threads” – those definitions are explained later on in the article). It is very easy to create a test with Jmeter – it has a recorder tool that lets you record your test by listening to a browser. Jmeter is a very handy tool to perform benchmarks and load tests. We created our benchmark test using Apache Jmeter. To do that, we first needed to perform a benchmark on a clean Magento installation – we chose Magento 2.2.4. *\ )ĥ) Make sure that you test this on your setup just as precaution to avoid issues with third party extensions etc.Few weeks ago, one of our customers asked to benchmark one of our extensions. So, once you download appropriate patch version, put it in your website root directory and execute the following command in your website root: patch -p1 \$.+\ \ (. Those are just regular *.patch files that you can apply on your system using patch or GIT. Once you find the patches, you might be surprised by their filenames, but there is nothing to be afraid of.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |