Requests dispatched and not yet answered.
Workers in the pool.
Terminates every worker. Outstanding requests reject.
Runs one envelope on the least-busy worker.
assemble is forced off — the pool answers columns, and the caller
assembles a TimeSeries from them if it wants one. Assembling
worker-side would build an object that cannot cross the boundary.
Pass affinity to pin related requests to one worker. Requests
sharing an affinity key land on the same host, so its warm nodes are
reused — worth it when a caller re-asks overlapping questions about
one dataset, and pointless when every request is unrelated.
Optionalaffinity: stringStaticstartStarts the pool and waits for every worker to be listening.
Setup modules are imported lazily inside each worker on its first
request, so start resolving does not mean the registry loaded — a
broken setup module surfaces as that first request's error, where a
caller can read it, rather than as a start-up crash with no
request to attach it to.
@pond-ts/process/pool— whole requests across resident workers.A separate entry point because it is Node-only (it imports
node:worker_threads); the package index stays runtime-neutral.See HostPool for which of the two parallelism shapes this is, and why this one comes first.