Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Custom runner for subdomain / independent workloads #415

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

camillobruni
Copy link
Contributor

@camillobruni camillobruni commented Jun 26, 2024

WIP PR to demonstrate a hacky approach to run workloads independently from the main runnner.

hosted version: https://chromium-workloads.web.app/speedometer/v3.0-custom/?developerMode=&domainPerIteration=true

- Subdomain running options:
  - hosted: using `-$ITER` subdomain suffix
  - local: using increasing port numbers
- Add measure prepare phase for "loading" style metric
- Move the warmup suite to the main config
- Display all top level metrics directly in the details view


The subdomain runner works by the outer default runner communicating
with the inner (embedded) runner via postMessage. There are 2 new
runners

- SubdomainBenchmarkRunner: the outer runner
- EmbeddedBenchmarkRunner: the inner runner

The main page switches over to the SubdomainBenchmarkRunner if the
corresponding param is set.
The EmbeddedBenchmarkRunner is then used by setting `?embedded` and
we end up with double wrapped workload (easy right...):

  SubdomainBenchmarkRunner:
    iframe:
      EmbeddedBenchmarkRunner:
        iframe:
           Suite

This approach doesn't require changing the current workloads and we
can still easily measure framework setup time. Hopefully this can
be cleaned up in the future by refactoring the runner.

Change-Id: Ib813e8d83fd164fb2849b6889f187c1904b21965
Force run a gc() (expose with `--js-flags=--expose-gc`) before and
after preparing a suite to limit potential ripple-effects from
previous tests.

Change-Id: Ia397b9e0aa8f5dabfb1dc4a69cfad9a7cf63ce60
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant