Lower the cost of each launched wp process
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 55/100
- Issue 類型
- 重構
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- php
- 領域
- performance, testing
研究方向
Consult #384 for baseline CI timings and #257 for Xdebug conditions. Find where the framework spawns wp processes (likely PHP test harness) and add logic to disable Xdebug unless coverage/debug is set, plus an opcode cache for WP-CLI and package code while excluding per-scenario WordPress copies. Done means a draft PR shows reduced CI run times recorded against the baseline.
由索引模型根據 Issue 內容生成。
描述
Almost all of the suite's run time is spent in the wp processes the scenarios launch; the Behat process itself accounts for about 3% of a run. Each wp call costs about 0.3 seconds, and the bundled commands make around 9,300 of them per suite run, plus the ones the framework makes itself.
Two things make each process more expensive than it needs to be:
- Xdebug. When Xdebug is loaded locally, every child process pays for it. Turning it off for the launched processes took a local
cache-commandrun from 126 to 98 seconds. It should stay off unless coverage is collected or step debugging is requested (see #257). - No opcode cache. Every process compiles WP-CLI and the package code from scratch, although that code does not change during a run. Caching only that code took a typical call from about 300 to 200 ms locally. The per-scenario WordPress copies must stay uncached: they are rewritten during scenarios, and a stale compiled file would change what a test exercises.
Measuring: take the baseline from #384, then open a draft PR, run the same CI jobs against it and record both results here before we decide.
- 主要語言
- PHP
- 星號
- 42
- 分支
- 29
- 平均合併
- 21 小時 6 分鐘
- 30 天內合併 PR
- 24
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
wp-cli/wp-cli-tests 的其他 Issue
-
scope:testing status:unconfirmed
難度 2/5 1-3 小時 新手友好度 65/100
wp-cli/wp-cli-tests#389 · 1 則留言 ·
維護者通常 1 天內回覆
-
os:windows scope:testing status:unconfirmed
難度 4/5 3-5 天 新手友好度 25/100
wp-cli/wp-cli-tests#427 ·
維護者通常 1 天內回覆
-
bug scope:testing
難度 4/5 3-5 天 新手友好度 22/100
wp-cli/wp-cli-tests#426 ·
維護者通常 1 天內回覆
-
scope:artifacts scope:distribution scope:testing
難度 4/5 3-5 天 新手友好度 25/100
wp-cli/wp-cli-tests#425 ·
維護者通常 1 天內回覆
-
scope:testing
難度 5/5 一週以上 新手友好度 20/100
wp-cli/wp-cli-tests#395 ·
維護者通常 1 天內回覆
查看 wp-cli/wp-cli-tests 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 3 天內回覆
-
sync-en
難度 2/5 1-3 小時 新手友好度 74/100
維護者通常 1 天內回覆
-
[Sync EN] Formatting improvements to "Large Objects (LOBs)" docs (#6056)可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉sync-en
難度 1/5 1 小時以內 新手友好度 74/100
維護者通常 1 天內回覆
-
Перевод устарел
難度 2/5 1-3 小時 新手友好度 73/100
維護者通常 1 天內回覆
-
repo:cms
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆