Where useful computation is lost
Scheduling, locality, memory traffic and coordination costs can leave a busy machine doing less useful work. The studies examine those constraints one at a time.
Our research examines how machines complete useful work, how operators investigate changing conditions, and how services recover. Rubian and Kestowv provide the operating foundation for Arcturus; the studies below explain the constraints and methods behind that work.
A working command-line operating environment used to exercise persistent users, services, files, projects, authenticated system connections, and benchmark work.
Explore Rubian →The systems layer, runtime model, process architecture, and source of coordination mathematics beneath the current work.
Understand Kestowv →Equal-work testing, correctness gates, repeated trials, telemetry, limitations, and the receipts behind named measurements.
Review the method →Operating-system scheduling, accelerators, memory, machine reliability, and the problems guiding Valen Systems' research.
Read the studies →Support continued engineering, disclosed testing, documentation, and the recovery of historical technical work.
Support the work →Troy Mallory invented Rubian and Kestowv and leads the technical direction behind Project Valux, Rubian, and Kestowv.
Meet the company →Troy Mallory contributed the builtin-tracking mechanism in JRuby PR 9174 after reporting validation in Kestowv. JRuby maintainers merged and expanded the contribution, which entered the JRuby 10.1 release line.
Systems research for data centers meets power, cooling, hardware state, workloads, recovery, and human operations at the facility. Continue to infrastructure
The research library connects machine constraints, recorded measurements and operating methods. Start with the question you need to answer, then inspect the work behind it.
Scheduling, locality, memory traffic and coordination costs can leave a busy machine doing less useful work. The studies examine those constraints one at a time.
Compare equal work and inspect correctness, conditions and limits. Throughput, response time and energy answer different questions.
Discovery, reusable commands, shared workspaces and service recovery have their own guides. They are not all the same operating problem.
Read the architectural history beside the specific upstream contribution and current technical direction.
Working through a hardware or runtime decision? Explore compute evaluations