From an idea to something real.
One agent-built project. Three graphics workflows. With and without the Shardflux GPU driver.
Loading the recorded runs
Reading the captured results.
Shardflux GPU driver
NVIDIA L4Click a desktop to control it. Expand either side for a full-size view.
Actual results, recorded on Shardflux.
How this comparison was run
These are recordings of real applications in a Shardflux VM. The agent created the editable drone, built the game, and used the product configurator. The same files, CPU and memory limits, and quality settings were used for both modes.
Recorded runs were measured separately to avoid contention. Blender compares Cycles CUDA with CPU rendering; its editor display uses software OpenGL on both sides. Godot compares Vulkan through Shardflux with Mesa llvmpipe. Chrome compares ANGLE Vulkan with SwiftShader. Frame rates describe application rendering, not the 30 fps video or the live desktop connection.
This is one paired demonstration, not a fleet benchmark. Startup, shader compilation, screen recording and shared GPU load can change timings. Blender values include all three measured render calls. Browser timing includes the scripted interactions. The local live desktops are separate matched VMs.
Read run measurements