perf(cli): establish built help and version startup baselines

Ouverte
#2,482 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
22/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
cli, nodejs, typescript
Domaine
cli, performance

Piste de recherche

Start with scripts/measure-cold-start.mjs and the built CLI's help and version entry points, but the build must first succeed: TypeScript and the locked dependency restore are currently blocked, and dist is absent. Add focused runner tests for missing dist, nonzero child exit, timeout and invalid samples, using deterministic inputs for quantile and output-shape checks. Done means three rounds of at least 20 fresh processes per command with raw observations, SHA, Node/platform details and p50/p95 published, with no performance claim.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Summary

Split the packaged CLI startup measurement out of the broader benchmark request github/squad#2476. This is a measurement-only issue for two commands: the built CLI's help and version entry points. It does not authorize startup optimization or a new benchmark framework.

Parent: github/squad#2481.

Proposed primary owner: cli-dev.

Existing evidence and blocker

At audited revision 47082a81799710c3e457b594123d190c00596ebf, scripts/measure-cold-start.mjs exists, but built CLI startup could not be measured. TypeScript was unavailable, locked dependency restoration returned a configured-feed E404 for hono-4.13.17.tgz, and dist was absent. There is no established startup latency or RSS result yet, and no startup bottleneck/speedup is claimed.

Use the existing built/shipping CLI entry point and runner after the documented restore/build succeeds. Source-loader or SDK-import probes are not substitutes, as illustrated by the packaged-path correction in microsoft/aspire#16704.

Scope

  • In: help/version process-start-to-exit wall time and process maximum RSS, existing runner output/error handling, portable reproduction instructions and raw artifacts.
  • Out: interactive shell/session resume, model calls, config/charter/memory/backend benchmarks, lazy-import changes, CI gates, cross-platform rollout and solving package-feed infrastructure in product code.

Measurable acceptance and tests

  • For each command, collect three rounds of at least 20 fresh child processes on the same recorded SHA/build/environment. Record first observations separately and label OS filesystem-cache state; do not describe warm-filesystem fresh processes as cold storage.
  • Publish every raw elapsed/RSS observation, exit status, exact command, SHA, Node/platform/build mode and per-round p50/p95. RSS must be labeled as process maximum RSS, not allocation volume or total agent-session memory.
  • Run without inference/network workload or user-home mutation. Verify expected help/version output and successful exit on every measured invocation; keep output equivalent to the unmodified built CLI.
  • Focused runner tests prove missing dist, child nonzero exit, timeout and missing/invalid measurement data fail explicitly rather than emit a successful zero/NaN sample. Quantile/output-shape tests use deterministic inputs.
  • Publish a portable command and shared results artifact; no dependency on a private Copilot session path. If restore remains blocked, retain the exact blocker and leave measurement acceptance incomplete.

Done means

A reproducible, correctly labeled baseline for these two commands and failure-sensitive runner tests. No performance improvement is required or claimed by this measurement issue. Any identified startup optimization requires its own narrowly scoped, measured follow-up. The rollup github/squad#2481 tracks this result.

Langage dominant
TypeScript
Étoiles
3.4k
Forks
516
Merge moyen
1 j 15 h
PR mergées (30 j)
116

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/squad

Toutes les issues de github/squad

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.