Different hardware. Same foundation.
RLX Infra has been measured across two substantially different test systems to validate local execution across both accelerated and CPU-only environments. The measured results are public; the internal implementation that produces them remains proprietary.
Measured validation results — not a build guide.
The figures on this page are measured snapshots from two separate RLX Infra validation systems. They are shown to demonstrate observed local performance, not to publish the underlying architecture. The two profiles use different models and workloads, so their numbers should not be read as a direct head-to-head benchmark. Routing logic, allocation strategy, model handling, scheduling, caching and optimization methods remain private to Realystic™ / RLX.
RLX Infra — Test Systems
Measured development validation profilesNVIDIA 16 GB-Class Validation Node
Measured local inference validation on a discrete NVIDIA GPU test system. Public results are shown below; the internal RLX orchestration and optimization methods used during the run are intentionally not disclosed.
Low-Power CPU Validation Node
A deliberately constrained CPU-only test environment used to validate local execution while normal desktop and remote workloads remain active.
What the Public Results Show
Measured evidence without implementation disclosureValidation Signals
Public Diagnostics Console
Measured public outputrealystic@skynet2:~$ rlx-infra verify --public-profile RLX Infra Measured Public Validation Test System A: Decode 132.7 tok/s // Prompt 16,987.4 tok/s // 2,186 tok // 16.8 s wall ... PASS Test System B: CPU ~1.87 tok/s // Context 2,048 // Cold load ~8.7 s .................... PASS Execution range: CPU-only through discrete-GPU local inference .......................... CONFIRMED Internal orchestration: [ PROPRIETARY / NOT DISCLOSED ] realystic@skynet2:~$ echo "Measured results public. Internal method private." Measured results public. Internal method private.