You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 29, 2019. It is now read-only.
Copy file name to clipboardExpand all lines: setup/performance-toolkit/README.md
+20-25Lines changed: 20 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
3
3
## Overview
4
4
5
-
The Performance Toolkit enables you to test the performance of your Magento installations and the impact of your customizations. It allows you to generate sample data for testing performance and torun Apache JMeter scenarios, which imitate users activity. As a result, you get a set of metrics, that you can use to judge how changes affect performance, and the overall load capacity of your server(s).
5
+
The Performance Toolkit enables you to test the performance of your Magento installations and the impact of your customizations. It allows you to generate sample data for testing performance and to run Apache JMeter scenarios, which imitate users activity. As a result, you get a set of metrics, that you can use to judge how changes affect performance, and the overall load capacity of your server(s).
6
6
7
7
## Installation
8
8
9
9
### Apache JMeter
10
10
11
-
- Go tothe[Download Apache JMeter](http://jmeter.apache.org/download_jmeter.cgi) page and download JMeter in the *Binaries* section. Note that Java 8 or later is required.
11
+
- Go to the[Download Apache JMeter](http://jmeter.apache.org/download_jmeter.cgi) page and download JMeter in the *Binaries* section. Note that Java 8 or later is required.
12
12
- Unzip the archive.
13
13
14
14
### JSON Plugins
@@ -58,7 +58,7 @@ The following parameters can be passed to the `benchmark.jmx` scenario:
58
58
| numberOfThreads | 48 | Total number of all threads. |
59
59
| frontEndPoolPercentage | 90 | Percentage of Frontend Pool. |
60
60
| adminPoolPercentage | 10 | Percentage of Admin Pool. |
61
-
|browseCatalogPercentage | 30 | Percentage of threads in Frontend Pool that emulate catalog browsing activities. |
61
+
|browseCatalogByGuestPercentage| 30 | Percentage of threads in Frontend Pool that emulate catalog browsing activities. |
62
62
| siteSearchPercentage | 30 | Percentage of threads in Frontend Pool that emulate catalog search activities. |
63
63
| checkoutByGuestPercentage | 4 | Percentage of threads in Frontend Pool that emulate checkout by guest. |
64
64
| checkoutByCustomerPercentage | 4 | Percentage of threads in Frontend Pool that emulate checkout by customer. |
@@ -68,15 +68,16 @@ The following parameters can be passed to the `benchmark.jmx` scenario:
68
68
| productCompareDelay | 0 | Delay (s) between iterations of product comparison. |
69
69
| promotionRulesPercentage | 10 | Percentage of threads in Admin Pool that emulate creation of promotion rules. |
70
70
| adminPromotionsManagementDelay | 0 | Delay (s) between creation of promotion rules. |
71
-
|merchandizingPercentage| 50 | Percentage of threads in Admin Pool that emulate merchandizing activities. |
72
-
| adminProductManagementPercentage | 90 | Percentage of threads in Merchandizing Pool that emulate product management activities. |
73
-
| adminCategoryManagementPercentage | 10 | Percentage of threads in Merchandizing Pool that emulate category management activities. |
71
+
|merchandisingPercentage| 50 | Percentage of threads in Admin Pool that emulate merchandising activities. |
72
+
| adminProductManagementPercentage | 90 | Percentage of threads in Merchandising Pool that emulate product management activities. |
73
+
| adminCategoryManagementPercentage | 10 | Percentage of threads in Merchandising Pool that emulate category management activities. |
74
74
| adminProductEditingPercentage | 60 | Percentage of threads in Product Management Pool that emulate product editing. |
75
75
| adminProductCreationPercentage | 40 | Percentage of threads in Product Management Pool that emulate creation of products. |
76
76
| adminCategoryManagementDelay | 0 | Delay (s) between iterations of category management activities. |
77
77
| apiProcessOrdersPercentage | 30 | Percentage of threads in Admin Pool that emulate orders processing activities. |
78
-
| adminProcessReturnsPercentage | 10 | Percentage of threads in Admin Pool that emulate creation/processing of returns. |
79
-
| csrPoolPercentage | 0 | Percentage of CSR Pool. |
78
+
| apiProcessOrders | 5 | Number of orders for process in Admin API - Process Orders |
79
+
| adminEditOrderPercentage | 10 | Percentage of threads in Admin Pool that emulate order edit |
80
+
| csrPoolUsers | 0 | Users of CSR Pool. |
80
81
| csrBrowseCustomersPercentage | 10 | Percentage of threads in CSR Pool that emulate customers browsing activities. |
81
82
| csrCreateOrderPercentage | 70 | Percentage of threads in CSR Pool that emulate creation of orders. |
82
83
| csrCreateProcessReturnsPercentage | 20 | Percentage of threads in CSR Pool that emulate creation/processing of returns. |
@@ -193,32 +194,26 @@ For more details, read [Summary Report](http://jmeter.apache.org/usermanual/comp
193
194
| Checkout By Customer | Checkout By Customer | 4 |
@@ -236,9 +231,9 @@ For example, the value of {numberOfThreads} parameter is 100 and we want to get
236
231
237
232
N = 100 * 90 * 4 / 10000 = 4
238
233
239
-
The *Merchandizing Pool* and the *Product Management Pool* should be taken into account when the number of product or category management threads needs to be calculated. For example, the number of threads in *Admin Create Product (Merchandizing)* group is calculated as follows:
234
+
The *Merchandising Pool* and the *Product Management Pool* should be taken into account when the number of product or category management threads needs to be calculated. For example, the number of threads in *Admin Create Product (Merchandising)* group is calculated as follows:
0 commit comments