Files

T

Mikhail 666a6587e8 Support jetstream and motionmark in perf (#25599 )

* supports --story-filter-exclude
* A new way to replace wpr .json
* Add rendering_story_set to record-wpr.json5
* add a missed fil
* Fix BenchmarkConfig
* Fix archive_data_file==''
* new scripts
* Add WPRs
* Update the scripts
* Update configs
* Fix presubmit
* Fix raising an error for Brave WPRs
* Add comments
* add --preseve-service-hosts

2024-09-19 11:30:18 +07:00

1.8 KiB

Raw Blame History

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 .sha1 files, to brave-core.

Updating profiles

Instruction

1.8 KiB Raw Blame History