feat(blender-run): --cpu runs with no GPU attached (modelling/IO jobs stay off GPU 3)

2026-09-28 14:23:12 -07:00
parent 5e6a6f3b26
commit a51188c76a
2 changed files with 16 additions and 4 deletions
@@ -48,6 +48,11 @@ scripts/blender-run -- --python-expr 'import bpy; print(bpy.app.version_string)'
  screen datablock's VIEW_3D area. Worked calls for every add-on:
  `scripts/blender-probes/extensions_acceptance.py`. Full notes and foot-guns: the stack README,
  section "Extensions".
+- **`--cpu`** attaches no GPU at all (no nvidia runtime), so the run never touches GPU 3. Use it
+  for modelling, add-ons and import/export, which is anything that does not render. It is proven
+  for those (the extension acceptance ran that way) and for Cycles on CPU. EEVEE and Workbench
+  are expected to fail without the GPU (untested). The container hostname is always
+  `fv-ml1-blender`.
 - **Budget:** each run is capped at 64 GB RAM and 48 CPUs, with up to the whole 96 GB of VRAM.
  Keep to about 2 concurrent renders. It is not on irv-ml1, so irv-ml1's working-set budget
  does not apply.