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

Aperta
#356 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
android, flutter, go, ios

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
6
Fork
3
Merge medio
6h 28m
PR unite (30g)
362

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AlphaWaveSystems/flutter-probe

Tutte le issue di AlphaWaveSystems/flutter-probe

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.