Repository navigation
ci: hosted 子进程启动耗时证据 (#81/#144/#40) #200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
31 changes: 31 additions & 0 deletions
31
research/ui/results/2026-10-30-hosted-startup-latency/README.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| # hosted windows-2025 的子进程启动耗时(#81/#144/#40 佐证) | ||
|
|
||
| 本片回答一个可测子问题:在托管镜像上,**纯进程启动**本身要多久,与 10–12 秒的固定期限相差多少。 | ||
|
|
||
| ## 方法 | ||
|
|
||
| dispatch-only 作业 `windows-2025-startup-latency`([工作流](../../../../.github/workflows/conpty-compat.yml)): | ||
|
|
||
| - `powershell.exe -NoLogo -NoProfile -NonInteractive -Command "exit 0"` × **100** 次; | ||
| - `node --version` × **50** 次; | ||
| - 每次新进程,15 秒超时,记录耗时、返回码、是否超时;统计 min/p50/p90/p99/max 与 ≥1s/≥5s/≥10s 计数。 | ||
|
|
||
| ## 结果(run 40935653206,windows-2025) | ||
|
|
||
| | 项 | 次数 | min | p50 | p90 | p99 | max | ≥1s | ≥5s | ≥10s | 超时 | | ||
| |---|---|---|---|---|---|---|---|---|---|---| | ||
| | PowerShell 5.1 | 100 | 0.109 s | 0.110 s | 0.125 s | 1.828 s | 1.828 s | 1 | 0 | 0 | 0 | | ||
| | Node | 50 | 0.000 s | 0.016 s | 0.016 s | 0.735 s | 0.735 s | 0 | 0 | 0 | 0 | | ||
|
|
||
| ## 解释 | ||
|
|
||
| - 空闲镜像上,PowerShell 5.1 启动中位数 **110 ms**、最慢 **1.828 s**;Node 更快(中位 16 ms、最慢 735 ms); | ||
| - 因此 `ps51` 在 CI 里出现 **10219 ms** 的 `timed_out`(#81)不能归因于启动成本;Node 夹具的 10 秒超时(#144)同理; | ||
| - 三处(ps51 10.2 s、纯 PowerShell 12 s、Node 10 s)都属于"纯启动/纯脚本、几乎无输出、刚好越过期限",与本次测得的正常分布相差 1–2 个数量级,指向**宿主级停顿**(安全扫描、VM 调度、存储阻塞)。 | ||
|
|
||
| ## 边界 | ||
|
|
||
| - 只测空闲镜像;未在完整 CTest 同时段、安全软件扫描中或并行负载下测量; | ||
| - 未修改任何期限、夹具或准备流程; | ||
| - 不能据此断定停顿的具体来源,只排除"启动成本"这一解释; | ||
| - 与 #144 的 Node 夹具计时(warm 63 ms、冷启动 1.47 s)互相印证。 | ||
60 changes: 60 additions & 0 deletions
60
research/ui/results/2026-10-30-hosted-startup-latency/validation.json
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,60 @@ | ||
| { | ||
| "schema": "termforge-hosted-startup-latency-v1", | ||
| "issues": [ | ||
| 81, | ||
| 144, | ||
| 40 | ||
| ], | ||
| "run": 40935653206, | ||
| "job": "windows-2025-startup-latency", | ||
| "platform": "windows-2025 hosted", | ||
| "commands": { | ||
| "powershell": [ | ||
| "powershell.exe", | ||
| "-NoLogo", | ||
| "-NoProfile", | ||
| "-NonInteractive", | ||
| "-Command", | ||
| "exit 0" | ||
| ], | ||
| "node": [ | ||
| "node", | ||
| "--version" | ||
| ] | ||
| }, | ||
| "counts": { | ||
| "powershell": 100, | ||
| "node": 50 | ||
| }, | ||
| "results": { | ||
| "powershell": { | ||
| "min": 0.109, | ||
| "p50": 0.11, | ||
| "p90": 0.125, | ||
| "p99": 1.828, | ||
| "max": 1.828, | ||
| "over_1s": 1, | ||
| "over_5s": 0, | ||
| "over_10s": 0, | ||
| "timeouts": 0 | ||
| }, | ||
| "node": { | ||
| "min": 0, | ||
| "p50": 0.016, | ||
| "p90": 0.016, | ||
| "p99": 0.735, | ||
| "max": 0.735, | ||
| "over_1s": 0, | ||
| "over_5s": 0, | ||
| "over_10s": 0, | ||
| "timeouts": 0 | ||
| } | ||
| }, | ||
| "interpretation": "Pure start-up cost is 1-2 orders of magnitude below the fixed fixture deadlines, so the observed 10-12 s timeouts cannot be explained by start-up cost.", | ||
| "limitations": [ | ||
| "idle image only; not under full CTest concurrency or AV scanning", | ||
| "no deadline or fixture change", | ||
| "does not identify the stall source, only excludes start-up cost" | ||
| ], | ||
| "performance_claim": false | ||
| } |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new job measures only 100 PowerShell launches and 50 Node launches on an otherwise idle runner, so observing no 10-second launch does not exclude rare startup delays in the failing CI environment. In particular, scanning, scheduling and storage stalls can themselves occur during process startup; they are not mutually exclusive explanations. Treating startup cost as ruled out could prematurely narrow the investigations in #81/#144/#40. Report the observed idle-run distribution and retain the timeout explanation as unresolved unless measurements from the failing workload distinguish startup from subsequent execution; update the equivalent conclusion in
validation.jsonas well.AGENTS.md reference: AGENTS.md:L12-L13
Useful? React with 👍 / 👎.