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
+58-67Lines changed: 58 additions & 67 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,8 @@ The Performance Toolkit enables you to test the performance of your Magento inst
19
19
20
20
## Quick Start
21
21
22
-
Before running the JMeter tests for the first time, you will need to first use the `php bin/magento setup:performance:generate-fixtures {profile path}` command to generate the test data. You can find the configuration files of available profiles in the folders `setup/performance-toolkit/profiles/ce` and `setup/performance-toolkit/profiles/ee`.
22
+
Before running the JMeter tests for the first time, you will need to first use the `php bin/magento setup:performance:generate-fixtures {profile path}` command to generate the test data.
23
+
You can find the configuration files of available B2C profiles in the folders `setup/performance-toolkit/profiles/ce` and `setup/performance-toolkit/profiles/ee`.
23
24
24
25
It can take a significant amount of time to generate a profile. For example, generating the large profile can take up to 4 hours. So we recommend using the `-s` option to skip indexation. Then you can start indexation manually.
25
26
@@ -55,9 +56,9 @@ The following parameters can be passed to the `benchmark.jmx` scenario:
As a result, you will get `jmeter.log` and `jmeter-results.jtl`. The`jmeter.log` contains information about the test run and can be helpful in determining the cause of an error. The JTL file is a text file containing the results of a test run. It can be opened in GUI mode to perform analysis of the results (see the *Output* section below).
121
+
As a result, you will get `jmeter.log` and `jmeter-results.jtl`. The`jmeter.log` contains information about the test run and can be helpful in determining the cause of an error. The JTL file is a text file containing the results of a test run. It can be opened in the GUI mode to perform analysis of the results (see the *Output* section below).
123
122
124
123
125
124
The following parameters can be passed to the `benchmark_2015.jmx` scenario:
@@ -145,7 +144,7 @@ The following parameters can be passed to the `benchmark_2015.jmx` scenario:
145
144
146
145
### Run JMeter scenario via GUI
147
146
148
-
**Note:** Use the GUI mode only for scenario debugging and viewing reports. Use the console mode for real-life load testing, because it requires significantly fewer resources.
147
+
**Note:** Use the GUI mode only for scenario debugging and viewing reports. Use console mode for real-life load testing, because it requires significantly fewer resources.
149
148
150
149
- Change directories to `{JMeter path}/bin/` and run `jmeter.bat`.
151
150
- Click *File -> Open (Ctrl+O)* and select `benchmark.jmx` file or drag and drop the `benchmark.jmx` file in the opened GUI.
@@ -189,57 +188,49 @@ For more details, read [Summary Report](http://jmeter.apache.org/usermanual/comp
189
188
190
189
## Additional Information
191
190
192
-
### Threads
191
+
### Scenarios
193
192
194
-
`benchmark.jmx` scenario has the following thread groups and default percentage breakdown:
193
+
`benchmark.jmx` scenario has the following pools and default percentage breakdown for each scenario:
CSR Browse Customers thread group contains 5 variations:
233
-
- View Odd Grid Pages (20%)
234
-
- View Even Grid pages (20%)
235
-
- Filtering (20%)
236
-
- Sorting (20%)
237
-
- Filtering and Sorting (20%)
224
+
| Scenario Name | % of Pool |
225
+
| -------------------------- | --------- |
226
+
| Browse Customer Grid | 10 |
227
+
| Admin Create Order | 70 |
228
+
| Admin Returns Management | 20 |
238
229
239
230
**Legacy Threads**
240
231
241
232
The `benchmark_2015.jmx` script consists of five thread groups: the setup thread and four user threads.
242
-
By default, the percentage ratio between thread groups is as follows:
233
+
By default, the percentage ratio between the thread groups is as follows:
243
234
- Browsing, adding items to the cart and abandon cart (BrowsAddToCart suffix in reports) - 62%
244
235
- Just browsing (CatProdBrows suffix in reports) - 30%
245
236
- Browsing, adding items to cart and checkout as guest (GuestChkt suffix in reports) - 4%
@@ -249,7 +240,7 @@ By default, the percentage ratio between thread groups is as follows:
249
240
250
241
In order to build an aggregate report from the results of the `benchmark.kmx` scenario run, use the script `generate-b2c.php` in the folder `setup/performance-toolkit/aggregate-report`.
251
242
252
-
The script parses the JTL file and generates an aggregate report in CSV format. The report consists of the 4 sections separated by two empty lines:
243
+
The script parses the JTL file and generates an aggregate report in CSV format. The report consists of the following four sections separated by two empty lines:
253
244
254
245
1. Summary information: Checkouts Per Hour, Page Views Per Hour and Test Duration (in seconds)
255
246
2. Aggregated information about all requests within each thread group (median time, average time, min/max, amount of hits per hour, etc.)
@@ -296,4 +287,4 @@ Find all rows with the label *Simple Product # View* and calculate the summary t
296
287
297
288
If you need information about the summary throughput of the *Checkout* actions, find the rows with labels *Checkout success* and make the same calculation.
298
289
299
-
For the total number of page views, sum up all actions, minus the setup thread.
290
+
For the total number of page views, you will want to sum up all actions minus the setup thread.
0 commit comments