Lower the cost of each launched wp process

Aberta
  • Algo errado?
#385 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
55/100
Tipo de issue
Refatoração
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
php
Domínio
performance, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

scope:testing

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:

  1. Xdebug. When Xdebug is loaded locally, every child process pays for it. Turning it off for the launched processes took a local cache-command run from 126 to 98 seconds. It should stay off unless coverage is collected or step debugging is requested (see #257).
  2. 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.

Linguagem predominante
PHP
Estrelas
42
Forks
29
Merge médio
21h 6min
PRs com merge (30d)
24

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de wp-cli/wp-cli-tests

Todas as issues de wp-cli/wp-cli-tests

Issues semelhantes

Mais issues de PHP

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.