~90 µs
Cell-local Reflex handoffMeasured through 4,096 logical Cells in the tested software path.
Platform & Architecture · Measured Performance
Execution Performance
A Cell can carry many workloads, rich policy, continuity, evidence and Reflex behavior without turning execution into a heavy control-plane operation. The measured software path stays in microseconds and sub-milliseconds.
Rich execution. Small software overhead. Physical truth before Reflex Movement.
At a Glance
Thousands of Cells. Many workloads inside one Cell. Small execution overhead.
0.746 µs
exact workload bindingMeasured at 64 workloads inside one tested Cell, with zero allocations.
<1 ms
large policy commit + durable proofRich execution semantics stay lightweight before Movement.
Cell Density
64× more logical Cells. Cell-local Reflex time stayed ~90 µs.
As the tested logical Cell population grew from 64 to 4,096, the Cell-local Reflex handoff stayed in the same narrow range. More Cells did not turn the local execution path into a growing coordination operation.
89.3 µs64 logical Cells
91.8 µs256 logical Cells
90.3 µs1,024 logical Cells
92.3 µs4,096 logical Cells
This is Cell-local Reflex Movement evidence: the Cell-local software handoff remained small as logical Cell density increased.
Many Workloads Inside One Cell
One Cell carried 64 tested workloads while exact binding stayed below one microsecond.
A Cell is not one Pod, one VM, or one process. One Cell can carry many workloads — processes, containers, VMs, services, or a larger execution environment such as a Kubernetes cluster.
In the measured software path, exact workload binding at 64 workloads inside one Cell took ~0.746 µs and performed zero allocations.
The point is simple: richer execution inside a Cell does not have to make workload selection or binding the bottleneck.
Measured Capability Matrix
Rich execution decisions remain microsecond- and sub-millisecond-scale.
| Measured area | Tested scale | Linux median / result | Plain-English meaning |
|---|---|---|---|
| Cell-local Reflex handoff | 4,096 logical Cells | ~92.3 µs | Essentially flat from 64 → 4,096 Cells. |
| Exact workload binding | 64 workloads in one tested Cell | ~0.746 µs | Sub-microsecond; zero allocations. |
| Per-workload execution decision | Canonical multi-workload decision | ~16.3 µs | Rich execution decision remains microsecond-scale. |
| Durable resource reservation | Contended / idempotent | ~45.3 µs | Committed resource reservation remains lightweight. |
| ACL policy commit | 256 rules | ~0.532 ms | Large policy set committed in sub-millisecond time. |
| FQDN / SNI / ALPN policy commit | 128 FQDN policies | ~0.323 ms | Rich DNS/L7 intent remains sub-millisecond to commit. |
| Durable physical-state proof | Exact map-entry ownership cycle | ~0.475 ms | Receipt-backed physical ownership remains sub-millisecond. |
| Interrupted Execution Recovery | Interrupted materialization | ~0.670 ms | Interrupted execution recovery remains sub-millisecond. |
| GPU binding | Per-workload physical contract | Capability proof | Workload-specific, cgroup-bound and receipt-verified; hardware timing remains a separate certification layer. |
Physical Truth Before Reflex Movement
Celluster proves the new execution before reroute or clone.
Performance is not useful if execution moves first and discovers problems later. Celluster prepares the new execution, verifies physical state, preserves continuity, and only then allows Reflex Movement.
ONE CELL
Workloads · Resources · Policy · DNS/L7 · Continuity · Evidence
↓
EXECUTION DECISION
Microsecond-scale software path.
↓
PHYSICAL PROOF
Sub-millisecond durable bookkeeping and receipt-backed ownership.
↓
READY TO ADAPT
New execution is prepared and verified while continuity is preserved.
REROUTE
Movement to a verified execution while preserving the Cell’s authored continuity.
CLONE
A verified new execution instance joins service under the Cell’s lineage and continuity contract.
Reroute and clone remain Reflex Movement outcomes, performed only after the new execution is prepared, verified, and continuity is preserved.
What the Numbers Mean
The software path is small. Real workload readiness remains real.
These measurements cover the Celluster software execution path. The remaining time belongs to actual workload readiness: startup, health, state, dependencies, devices and the physical environment.
Measured here: Reflex handoff, workload binding, execution decision, resource reservation, policy commit, durable proof and recovery bookkeeping.
Separate physical evidence layers: DNS query latency, packet timing, GPU hardware latency, workload startup and device-specific readiness.
Five-run Linux medians on Intel Core i9-9980HK. Software execution path; hardware-specific timings require physical certification.
The Performance Story
Celluster adds execution meaning while keeping software overhead small.
More Cells, more workloads, richer policy and physical proof remain bounded in the measured software path. The architecture stays centered on the Cell: authored intent, evidence, Reflexes, continuity and verified Movement.