brave-buildsandbrave-builds-ro
706baf0c43
* Update perf profile brave-typical-mac using v1.90.84 * Update perf profile brave-typical-android using v1.90.48 * Update perf profile chrome-typical-mac using v1.90.84 * Update perf profile chrome-typical-android using v1.90.48 * Update perf profile brave-typical-win using v1.90.86 * Update perf profile chrome-typical-win using v1.90.86 --------- Co-authored-by: brave-builds-ro <devops+robuilds@brave.com>
Brave performance tests
Job URLs
S3 migration
Perf data is currently moving to AWS S3 brave-perf-data bucket.
The data is accessible via https://perf-data.s3.brave.com/{path}.
The current structure:
./perf-profiles/: test perf profiles
./telemetry-perf-data/: WPR files and other data are used by telemetry and
catapult code
S3 upload
- Make sure that you setup aws cli tools.
- Run
brave/tools/perf/perf_utils.py s3-upload <filename>.wprgo
GSC manual upload (legacy)
upload_to_google_storage.py --bucket=brave-telemetry <file>
the script will produce .sha1 automatically.
How to update or record WPR
Use npm run perf_tests -- --mode record-wpr instead of chromium update_wpr or record_wpr. It:
- downloads and runs both Brave and Chromium, combine .wpr files (to capture all browser-specific requests);
- adds pre-initialied profiles and Griffin/Finch experiments;
- does some pre runs to ensure that everything is initialized (aka online profile rebase)
- removes unwanted URLs from the final .wpr file.
Workflow
- Prepare a config (use configs/record-wpr.json5 as a base). One benchmark or storySet = one .wpr.
- Run
npm run perf_tests -- <config>.json5 --mode record-wpr --working-directory=.. --variations-repo-dir=..; - Run the matching benchmark locally to tests the created .wpr;
- Upload wpr files to the cloud storage:
ls ./brave/tools/perf/page_sets/data/*.wprgo | xargs <upload_cmd>; - Commit the changes, including a new
.sha1files, to brave-core.