Roll WebAI Compute Benchmark from 6521ac8afa5a to 253976fce9a0 (1 revision)

https://chromium.googlesource.com/external/github.com/GoogleChrome/webai-compute-benchmark.git/+log/6521ac8afa5a..253976fce9a0

2026-05-01 brendan.dahl@gmail.com Add experimental gemma.cpp WASM benchmark (#132)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webai-compute-benchmark-web-workload
Please CC cbruni@google.com,dlehmann@google.com,rezvan@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in WebAI Compute Benchmark: https://github.com/GoogleChrome/webai-compute-benchmark/issues
To file a bug in Web Workload: https://issues.chromium.org/u/1/issues/new?pli=1&component=1457389

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Tbr: cbruni@google.com,dlehmann@google.com,rezvan@google.com
Change-Id: Id4087baf23552fc1a0e83360239d48ecd0510d4e
Reviewed-on: https://chromium-review.googlesource.com/c/web-workload/+/7808311
Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com>
2 files changed
tree: 2c040f9f0fb3cc1c5994304928fc789812dac06d
  1. help/
  2. public/
  3. .firebaserc
  4. .gitignore
  5. .gitmodules
  6. .style.yapf
  7. .vpython3
  8. build.py
  9. deploy-main.sh
  10. deploy-subdomains.sh
  11. DEPS
  12. firebase.json
  13. LICENSE
  14. README.md
  15. setup.sh
  16. stage-main.sh
  17. test-deployment.py
README.md

Chromium Workloads

This is the source for the chromium workloads page. We keep copies and versions of common press benchmarks and other statically hosted workloads here.

Workloads might have custom licenses that can be found in their respective folders.

It consist of 3 parts:

  • The workloads.json description file with all workloads.
  • Workloads (e.g. existing press benchmarks) in the public folder.
  • The html / javascript code to display the data from workloads.json.

Workloads

If possible workloads are DEPS-rolled from single-version branches. on forked repositories on https://chromium.googlesource.com.

LICENSEs are part of the respective workloads or workload versions.

Sources

Setup ⚒️

mkdir web-workload && cd web-workload;

# Checkout using depot_tools's fetch command:
fetch web-workload;
cd web-workload

# Setup firebase login:
# - Install the firebase cl: https://firebase.google.com/docs/cli#install_the_firebase_cli
# - Setup firebase:
./setup.sh

Deployment 🚀

chromium-workloads is hosted on firebase.

  • Use stage-main.sh to stage a testing version for the main page on temporary domain (can be used for testing freely)

Danger Zone 😱

Update and Redeployment

  • git pull
  • gclient sync
  • Testing:
    • ./stage-main.sh
    • Quickly manually very that main page and benchmark versions load correctly.
    • Run the latest tracked benchmark versions.
  • Deployment:
    • Deploy using ./deploy-main.sh
    • Also deploy the subdomain hosting ./deploy-subdomains.sh

Emergency Rollback 😰

In case of a broken deployment we can manually restore an old version via the firebase console. firebase console

  • Open the firebase console
  • Open “Hosting”
  • “View” main “chromium-workloads” site
  • “Restore” one of the “Previous releases”