perf: frame_time and slow_frames flap on same-build reruns on emulators and simulators

Offen
#356 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
android, flutter, go, ios

Rechercherichtung

Read the performance metric comparison and window handling code, then inspect the tests for frame_time, slow_frames, and cpu on Android emulators and iOS simulators. The issue lists several possible directions, including repeated measurement runs, metric tolerances, or changing which metrics are gated, but does not settle on one. Done means the chosen behavior reduces same-build rerun failures and is covered by tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement

Observation

On a same-build rerun against a fresh --measure-all baseline, the default gated metrics still flap on an Android emulator (profile build) and an iOS simulator (debug): across three reruns 35 to 57 of ~105 tests failed on frame_time, slow_frames and some cpu; memory and data never failed. Only about 12 of 105 distinct failing (test, metric) pairs recurred in all three runs, so it is noise, not host load. On iOS 5 tests failed on frame_time alone (for example 22.8 ms vs 33-36 ms). --perf-metrics all flaps much more (frame_max, memory_growth, cpu_peak).

Ideas for 0.25

  • Compare the median of N windows (--perf-runs N) instead of one run.
  • A wider default tolerance or a per-metric tolerance for frame metrics.
  • Gate only memory, cpu and data on simulators and emulators by default, and document frame metrics as informational there (see #354 for the fixed 16.7 ms budget).

Smaller wording items

  • In compare mode the message "left out of the baseline" should say "skipped"; windows that span a restart are counted twice (as "no entry" and as "span an app restart").
  • open the app inside a window is not flagged as a restart (on iOS it may only foreground the app).

Scheduled after the stable 0.24.0 release.

Vorherrschende Sprache
Go
Sterne
6
Forks
3
Ø Merge
6 Std. 28 Min.
Gemergte PRs (30 T.)
362

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus AlphaWaveSystems/flutter-probe

Alle Issues in AlphaWaveSystems/flutter-probe

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.