Benchmark Results

Automated test suite performance tracking for Windows platform.

Desktop charts (no GitHub Pages needed): docs/desktop/README.md

Interactive dashboard → (requires GitHub Pages — enable in repo Settings → Pages → master / /docs)

Interactive charts grouped by scenario (community, wallet, swap). Updated nightly by Jenkins.

System info (desktop)

Nightly Jenkins runs collect Windows host metadata and pass it to benchmark.py parse via --machine-info. The dashboard System info block reads from data/run_environment.csv.

powershell -File scripts/collect_machine_info.ps1 -OutputPath machine_info.json
python scripts/benchmark.py parse --benchmark-dir <dir> --commit-hash <hash> --date <iso-date> --machine-info machine_info.json

See scripts/machine_info.example.json for the JSON shape. Wired in status-app/scripts/push_benchmark.sh.

Adding new tests

How to add a new performance test
  1. Edit ./scripts/tests_config.toml:
[[tests]]
test_id = "test_my_feature"
display_name = "My Feature Loading Time Performance"
graph_filename = "my_feature_loading_time.png"
pattern = "test_my_feature"
ylabel = "Load Time (s)"
  1. Add the test to a scenario page (or create a new one):
[[pages]]
slug = "my-feature"
title = "My Feature"
description = "Short description shown on the dashboard."
test_ids = ["test_my_feature"]
  1. Merge the change. Jenkins runs python scripts/benchmark.py graphs on the next scheduled run — it writes PNG + interactive HTML charts to docs/desktop/ and regenerates the GitHub Pages site.

  2. One-time setup: enable GitHub Pages in repo settings → Build and deployment → Source: Deploy from a branch → Branch: master / folder: /docs.

Android benchmarks

See docs/android/README.md for mobile navigation response time charts.


Raw CSV history: data/

S
Description
Benchmark metrics for windows e2e tests app timings with 60-day history and latest comparison.
Readme
1.3 GiB
Languages
Python 99.2%
PowerShell 0.8%