Skip to content

[suites-experimental] Add Angular Tools-GPS-Tracks workload - #601

Merged
camillobruni merged 10 commits into
WebKit:mainfrom
camillobruni:GPS-Tracks-Angular
Nov 13, 2026
Merged

camillobruni merged 10 commits into
WebKit:mainfrom
camillobruni:GPS-Tracks-Angular

Conversation

@camillobruni

Copy link
Copy Markdown
Contributor

Introduce an Angular-based implementation of the experimental GPS activity track analyzer workload to evaluate Angular component rendering alongside binary and XML telemetry parsing, IndexedDB persistence, geospatial mapping, and multi-track physiological charting in Speedometer.

Introduce an experimental GPS activity track analyzer workload to cover binary and XML telemetry parsing, IndexedDB persistence, geospatial map rendering, and multi-track physiological charting in Speedometer.
Expand the geospatial and physiological telemetry computations across all seven benchmark steps so each step consistently exceeds 20 ms on desktop Firefox while keeping iteration variance low.
Scale down the geospatial and physiological telemetry computations across all seven benchmark steps by 40% to keep total step runtimes balanced across browsers.
Achieve target step runtimes by exercising multi-track, multi-section, and multi-mode application workflows instead of repeating identical computations in synthetic loops. This keeps all 7 benchmark steps balanced at ~40-60ms in Firefox while testing realistic user interactions across all views.
Browser history state updates are rate-limited across repeated benchmark iterations and cause SecurityError failures in high-iteration runs. Replace window.history usage with an in-memory query and navigation state implementation so benchmark runs execute without browser history side effects.
Re-implement the Tools-GPS-Tracks benchmark workload using Angular 19 standalone components, reactive state management, and template-driven change detection across all six analysis views while preserving full feature parity and deterministic benchmark steps.
@netlify

netlify Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for webkit-speedometer-preview ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit e48070e
🔍 Latest deploy log https://app.netlify.com/projects/webkit-speedometer-preview/deploys/6af74b60fc1b31f593aaef98
😎 Deploy Preview https://deploy-preview-601--webkit-speedometer-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@camillobruni
camillobruni requested a review from Bas-moz November 13, 2026 16:17
Rename the Angular GPS tracks benchmark suite and directory to Tools-GPS-Tracks-Angular / tools-gps-tracks-angular so it can coexist alongside the vanilla implementation without name collisions.
… step

Angular bootstrap and the synthetic warmup ran during prepare, producing a large unmeasured chunk before readiness. Prepare now only fetches test data, and bootstrap plus per-tab component creation happen inside the measured steps on every iteration.
mstange pushed a commit to mozilla/Speedometer that referenced this pull request Nov 13, 2026
An Angular implementation of the Tools-GPS-Tracks workload, taken from
WebKit#601 at 0ef4d73. That PR replaces the vanilla
tools-gps-tracks workload; sp4-exp keeps both, so this adds the
tools-gps-tracks-angular directory and suite entry next to it.
# Conflicts:
#	.eslintignore
#	.prettierignore
#	suites-experimental/suites.mjs
@camillobruni
camillobruni merged commit fe0f6e5 into WebKit:main Nov 13, 2026
8 of 9 checks passed
@camillobruni
camillobruni deleted the GPS-Tracks-Angular branch November 13, 2026 17:43
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.

2 participants