Skip to content

docs: the environment side needs neither CUDA nor a GPU - #12

Merged
tactino merged 1 commit into
mainfrom
docs/gpu-free-result
Sep 19, 2026
Merged

tactino merged 1 commit into
mainfrom
docs/gpu-free-result

Conversation

@tactino

@tactino tactino commented Sep 19, 2026

Copy link
Copy Markdown
Member

The home page stopped at a VLA ran end to end through the boundary. Since then two experiments measured what the environment side actually costs, and that is the part a reader can act on.

The new section, in both languages

  • 3.4G with no nvidia wheels, against 7.8G with sixteen, sending byte-identical observations.
  • Renders on the CPU: ten clients at once, 30 of 30 episodes successful.
  • 1.91x wall clock, and the section says so in its second paragraph rather than leaving it for a reader to discover. Stepping is 10x slower in software; most but not all of that hides behind the queue of clients waiting on one policy.

It also says what it overturns

E1 measured a robomimic-class env client at 7.2G with CUDA and concluded the environment side does need a GPU. That was true of a default install - on Linux torch brings CUDA whether or not anything uses it. E12 reproduced E1's row exactly before changing one pin, which is what makes the two comparable, and E13 measured the rendering cost.

mkdocs build --strict passes.

The home page said a VLA runs end to end through the boundary and stopped there. The result worth arriving for is what the environment side now costs: 3.4G with no nvidia wheels instead of 7.8G with sixteen, rendering on the CPU, ten clients, 30 of 30 episodes, at 1.91x wall clock.

The section leads with that and then gives the catch, because 1.91x is the difference between a measurement and a slogan. It also says plainly that this overturns E1, which had concluded the opposite from a default install.
@tactino
tactino merged commit 769dcf7 into main Sep 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant