Skip to content
This repository was archived by the owner on Apr 29, 2019. It is now read-only.

Commit 3c6d09c

Browse files
committed
MAGETWO-83347: Benchmark updates
1 parent c6aabe3 commit 3c6d09c

File tree

11 files changed

+70
-1173
lines changed

11 files changed

+70
-1173
lines changed

setup/performance-toolkit/README.md

Lines changed: 0 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -236,32 +236,6 @@ By default, the percentage ratio between the thread groups is as follows:
236236
- Browsing, adding items to cart and checkout as guest (GuestChkt suffix in reports) - 4%
237237
- Browsing, adding items to cart and checkout as registered customer (CustomerChkt suffix in reports) - 4%
238238

239-
### Results Interpretation
240-
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`.
242-
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:
244-
245-
1. Summary information: Checkouts Per Hour, Page Views Per Hour and Test Duration (in seconds)
246-
2. Aggregated information about all requests within each thread group (median time, average time, min/max, amount of hits per hour, etc.)
247-
3. Aggregated information about common requests (open home page, category page, product page, login, etc.) across the entire scenario
248-
4. List of the requests that weren't executed during the scenario run
249-
250-
Also, the aggregate report can include information about the memory usage for each request type. This requires additional configuration. You should add the following code at the end of `pub/index.php`:
251-
252-
if (strpos($_SERVER['REQUEST_URI'], '/banner/ajax/load/') === false) {
253-
if (!file_exists('../var/log/memory_usage.log')) {
254-
file_put_contents('../var/log/memory_usage.log', str_pad('Usage', 12, ' ', STR_PAD_LEFT) . ' ' . str_pad('Real Usage', 12, ' ', STR_PAD_LEFT) . ' URI' . "\n", FILE_APPEND | LOCK_EX);
255-
}
256-
$result = str_pad(memory_get_peak_usage(), 12, ' ', STR_PAD_LEFT) . ' ' . str_pad(memory_get_peak_usage(true), 12, ' ', STR_PAD_LEFT) . ' ' . $_SERVER['REQUEST_URI'];
257-
file_put_contents('../var/log/memory_usage.log', $result . "\n", FILE_APPEND | LOCK_EX);
258-
}
259-
After that, the information about memory usage for each request will be logged in the file `var/log/memory_usage.log`.
260-
261-
To generate the aggregate report, run the following command from the Magento root directory:
262-
263-
php setup/performance-toolkit/aggregate-report/generate-b2c.php -j {path to folder with JTL file}/jmeter_report.jtl -m var/log/memory_usage.log -o aggregate_report.csv
264-
265239
**Legacy Scenario**
266240

267241
It is convenient to use *Summary Report* for the results analysis. To evaluate the number of each request per hour, use the value in the *Throughput* column.

0 commit comments

Comments
 (0)