* add scalability setup for login and promotion_tracking_dashboard journeys, re-enable step on ci
* update query to get single ftr transaction
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [ci] extract apm traces after in single user benchmarking pipeline
* add performance-testing-dataset-extractor dependency
* use BUILD_ID for queries
* bump version for extractor, update script
* bump extractor version
* fix path
* upload artifacts to the public bucket
- Removes user input and env var for performance test iterations
- Changes performance test execution queue
- Removes parallelism, queue mechanisms
- Removes dynamic creation of performance sub-steps
Co-authored-by: Spencer <spencer@elastic.co>
add performance tests for Login and Home pages
- [x] Rename and reduce the number of environment variables for performance test CI job
- [x] ITERATION_COUNT_ENV => PERF_TEST_COUNT
- [x] DISABLE_CACHE, TEST_RUNNER, TEST_THROTTLE_NETWORK removed
- [x] Use c2-16 queue for performance tests
- [x] Run performance tests by running ES and Kibana separately
- [x] Add warmup phase to performance tests (Not reported to APM). APM Label: PERF_TEST_PHASE
- [x] Add playwright dependency
- [x] Throttle network speed ( downloadThroughput: 750.000 B/s, uploadThroughput: 750.000 B/s, latency: 100 ms )
- [x] Disable cache by using - page.route (‘**’, ….)
- [x] Login and Home pages performance tests.
Concurrency parameters were not in the correct place which made concurrency settings not in effect.
Moved it to to performance.sh step which also has parallelism in the same level.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Adds auto and manual performance tests
If "ITERATION_COUNT_ENV" exist in build job:
- Auto Mode: Checks "ITERATION_COUNT_ENV",
- Manual Mode: Waits for user input,
use provided value to run "n" number of performance tests on parallel
- Sends slack notifications when pipeline finished
