Documentation
¶
Overview ¶
Command deploy_p50 is Load Experiment 7: the time of a code-only deploy and the warm-up of the pool after it (#1892).
It drives the real `dexaflow deploy` binary, as a user does. It scaffolds a project with `dexaflow init`, gives it pinned dependencies and a registry, and deploys it once cold: that deploy builds the dependency image (or finds it) and is discarded. It then makes n code-only changes to dag.py, one per deploy, and times each deploy from the start of the command to its exit. Each measured deploy must take the code-layer path of ADR 0077 (the registry holds the dependency image, only the code layer is pushed); a deploy that took another path fails the measurement, because it did not measure a code-only deploy.
With --warm it also measures the warm-up of each new version's pool on a cluster with warm pools on (ADR 0082): the project declares min_idle_workers: 1 and deploys with --active, and after each deploy the harness polls the warm worker pods for one running the new version's image, recording when it appeared, when it became Ready and the image pull time the kubelet reported.
It prints a Markdown table and a PASS or FAIL line, and exits 1 on FAIL.
Usage (see test/load/README.md, Experiment 7):
go run ./test/load/deploy_p50 --cli bin/dexaflow --config cli.yaml \ --registry k3d-registry.localhost:5111 --n 10
Source Files