// the vx blog
Posts tagged execution.
ExecutionDTE workers that fit the work, and a footer that says how full they ran
vx DTE puts each task on a machine type that can run it, books it by its measured memory peak and CPU, stops a server once nothing needs it, and prints how busy every worker was.
ExecutionA DTE relay that stores nothing
vx DTE's relay keeps no message, no timer and no storage row. It passes frames between sockets, and the two ends make sure each one lands.
Execution$12k a year saved with vx vs Nx Cloud
vx's CI is one run spread over its own Linux and Mac runners. On Nx Cloud's Team plan with Nx's agents, the same CI would cost about $12,192 a year. On vx it costs $0.
PerformanceWhich task runs first?
When more tasks are ready than workers, a runner has to pick. Five rules for picking, the graphs where each one wins and loses, measured with vx, and why recorded timings beat every rule that has to guess.
PerformanceHow many tasks at once? Count the cores you are given
In a container, the CPU count a program sees is the host's. vx reads the limit the kernel enforces, so it never starts more tasks than you have cores.
DXOne failure, and exactly what it takes down
A broken build skips only what depends on it, and each skip names the failure. One flag picks fail-fast or run-everything.
DXWhen a task misbehaves
A task hangs, gets killed, prompts for input, or calls vx run on itself. vx tells you what happened in one line.
ExecutionOne command per task; the shell is the API
A vx task is one shell command. That one rule is why remote runs, the sandbox and cache replay all work without special cases.
DXDev servers as graph nodes: readiness instead of sleep
vx waits for the line your dev server prints before starting the tests, and stops the server when the run ends. No sleep 5.
ExecutionCtrl-C leaves nothing running
Press Ctrl-C and every process vx started is gone within two seconds. Every way a run can end goes through the same teardown.
DXWatch: a content gate, not an event storm
vx watch lets the cache key decide what runs. A README edit runs nothing, a source edit runs exactly what it reaches.
