mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 02:09:32 -04:00
f5975d28fa
## Summary It’s common request for Dev teams to run specific journeys on a PR to compare performance metrics against the `main` branch. These requests usually focus on a particular area, such as the Dashboard or Discover app. To streamline the process, this PR groups relevant journeys into categories that can be triggered through an environment variable. For example, setting `JOURNEYS_GROUP=dashboard` will execute only the three dashboard-specific journeys, which are (usually) sufficient for evaluating the performance impact of code changes within the Dashboard app. Current Process for Triggering Performance Builds: - Create a new kibana-single-user-performance [build](https://buildkite.com/elastic/kibana-single-user-performance#new) - Provide the following arguments: Branch: `refs/pull/<PR_number>/head` Under Options, set the environment variable: `JOURNEYS_GROUP=<group_name>` Currently supported journey groups: - kibanaStartAndLoad - crud - dashboard - discover - maps - ml [Build example ](https://buildkite.com/elastic/kibana-single-user-performance/builds/14427) Each group focuses on a specific set of journeys tied to its respective area in Kibana, allowing for more targeted performance testing. Since running group takes ~5-10 min on bare metal worker, it should not delay the regular (every 3h) runs against `main` branch test locally with `node scripts/run_performance.js --group <group_name>` |
||
|---|---|---|
| .. | ||
| adding_api_capacity_test.mdx | ||
| adding_custom_performance_metrics.mdx | ||
| adding_performance_journey.mdx | ||
| running_performance_journey_in_cloud.mdx | ||