Memory Usage


In Phoenix, if you load the same cache frame into several Simulators (via the Input rollout), the cache's data is automatically shared between the Simulators and does not use extra memory. This holds for both copies and instances of the Simulator.

If you render several Simulators in Volumetric or Volumetric Geometry render mode, there are a few options that would use extra memory per each Simulator, regardless if it's a copy or instance. Using these settings might also overflow your RAM if you are loading large sparse cache files:

Render Speed


Using Grid-based Self Shadowing or Optimize Big Volumetric Grids would also add a rendering pre-pass stage for each of the Simulators in the scene.

All important tips for fast rendering of single volumes apply to many instances as well, please check the Volumetric Rendering In-Depth for more information.

V-Ray GPU


Note that if you have many overlapping volumes, V-Ray GPU can render an infinite number of volumes in the scene, but no more than 4 volumes that overlap at the same position in space.