ci: sample runner memory pressure during iOS E2E (diagnostic)#172
Draft
V3RON wants to merge 8 commits into
Draft
ci: sample runner memory pressure during iOS E2E (diagnostic)#172V3RON wants to merge 8 commits into
V3RON wants to merge 8 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Add a second sampler logging full `ps -Ao rss,pid,command` every 10s, plus a peak-snapshot per-process/grouped breakdown in the step summary, to attribute the 7 GB runner pressure to specific processes.
ps RSS double-counts shared framework memory, inflating simulator totals absurdly. Switch the per-process sampler to `top -l1 -o mem` (phys_footprint, Activity Monitor's metric) plus PhysMem total and process count.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a lightweight memory-pressure sampler to the
e2e-iosjob: a backgrounded loop logsvm.swapusage+vm_statevery ~2s across the harness run, a step-summary reports peak swap / compressed / free + swapout delta, and the raw log is uploaded as an artifact (mem-pressure-e2e-ios).Why
Investigating why the iOS harness takes >5 min on the standard
macos-latestrunner (3 vCPU / 7 GB). This probe confirms whether the box swaps while simulator +xcodebuild+ Metro run together.Result from run 29996372090 (this branch, Xcode 26.6)
Harness step ~322s. During it:
Conclusion: the 7 GB runner is memory-constrained; compression (CPU work) amplifies the 3-vCPU bottleneck. Informs whether to move to a larger runner and/or reclaim simulator RAM.
Note
Diagnostic instrumentation — cheap (
sysctl/vm_statonly) andif: always()-guarded. Keep it gated for ongoing visibility, or revert after the sizing decision.