Skip to content

Keep local iPhone performance capture running during normal app use - #17

Closed
AlexSchmidt1999 wants to merge 2 commits into
codex/today-pending-sync-layoutfrom
codex/local-performance-capture
Closed

AlexSchmidt1999 wants to merge 2 commits into
codex/today-pending-sync-layoutfrom
codex/local-performance-capture

Conversation

@AlexSchmidt1999

Copy link
Copy Markdown
Owner

Keep Display & Performance running across the iPhone app while its existing Test Centre mode is enabled. Previously leaving Test Centre stopped the monitor, so Today and Trends could not be captured during normal use.

The app now owns foreground capture, with one display link, five-second summaries, actual-cadence late-callback counts, primary-tab context, process CPU/memory, thermal state, Low Power Mode and history-sync state. A separate 2 MiB archive reuses StrapLogArchive so verbose sync logs do not evict performance captures; reviewed Display/Master exports include performance.txt. The mode remains default-off and persists through the existing preferences. Nearest-rank p95 indexing and a Test Centre test-isolation issue are corrected.

Initial local Instruments recordings on installed Release build 443 measured 39 Today and 77 Trends hitch events; after the first ten seconds, 22 and 47 remained respectively, with worst delays of 62.51 ms and 216.69 ms. These interactive captures include profiler overhead and establish symptoms, not a confirmed root cause or improvement. Raw traces stay local; only aggregate timings are included here.

Validation: macOS app compiled with 57 targeted monitor, activation, archive and report tests passing; iOS Release app, widgets and watch compiled; translation, doc-comment and diff checks passed; source and four-bundle binary security policies passed. Build 444 was installed and launched on the owner's iPhone through the existing local installation process. After enabling the existing mode, 26 persisted summaries from More, Today and Trends were copied back and verified; capture continues after leaving Test Centre. No upstream PR, release or automation was started. Android is explicitly outside the requested scope; no physiological analytics, stored values, schema, AI settings or temperature defaults change.

Longer on-device capture and collector overhead still require ordinary-use validation. See docs/FORK_PERFORMANCE_TESTING.md for the test sequence and export limits.

@AlexSchmidt1999

Copy link
Copy Markdown
Owner Author

Closing this older fork test PR. Its full head (7a130b1e9d78) is included in the combined test branch. New test-version work continues in #28. The branch and commits are kept.

The relevant changes are now submitted for upstream review in #2758.

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