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

未关闭
#356 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
android, flutter, go, ios

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Go
星标
6
派生
3
平均合并
6 小时 28 分钟
30 天内合并 PR
362

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AlphaWaveSystems/flutter-probe 的其他 Issue

查看 AlphaWaveSystems/flutter-probe 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。