Results with the test beside them.

Engineers, researchers, and enterprise buyers

Every public number names the work, release, method class, result, correctness status, and limitation.

69.669x faster directory listing.

Median result for one in-process Rubian operation against the named process-start comparison. The result doesn’t support a generic shell or operating-system superiority claim.

5,082.148 bridge requests per second.

One qualification completed every accepted request with zero correctness errors.

1,512,206 work units per second.

One equal-work Kestowv control completed every accepted work unit with matching checksums. The result belongs to that named control condition.

Read the result in context.

Each summary identifies the tested component, work, method, correctness status, result, and limitation.

Project Valux needs its own results.

Existing Rubian and Kestowv measurements don’t automatically describe Project Valux. New claims require matched work, correctness checks, telemetry, and repeated trials.

Working through a hardware or runtime decision? Explore compute evaluations