# Progressive Mode - Understanding Ray Bundle Size

**URL:** <https://forums.chaos.com/t/progressive-mode-understanding-ray-bundle-size/50357>\
**Category:** General\
**Created:** [July 3, 2014, 8:46am UTC](https://forums.chaos.com/t/progressive-mode-understanding-ray-bundle-size/50357 "2014-07-03T08:46:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexyork](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/alexyork/32/271382_2.png) [@alexyork](https://forums.chaos.com/u/alexyork)\
**Post date:** [July 3, 2014, 8:46am UTC](https://forums.chaos.com/t/progressive-mode-understanding-ray-bundle-size/50357/1 "2014-07-03T08:46:46Z")

</div>

Hi folks,

Vlado has mentioned that in order to maximise DBR efficiency you need to give your nodes enough work to do, so the best way to do this is to increase the Ray Bundle Size value.

Two questions:

1) raise it to what? what’s a safe boundary? 256? 512? 1024?  
2) the default is 128 - if we’re only using 1 local machine for rendering, are we better off lowering this? to 64? 32? 16?

Some guide for the values’ top and bottom ends would be really helpful to understand this. The amount of time I have for experimentation is extremely limited these days.

Thanks,

---

<div class="post-metadata">

**Author:** ![Dariusz\_Makowski\_Dadal](https://avatars.discourse-cdn.com/v4/letter/d/c4cdca/32.png) [@Dariusz\_Makowski\_Dadal](https://forums.chaos.com/u/Dariusz_Makowski_Dadal)\
**Post date:** [July 3, 2014, 10:07am UTC](https://forums.chaos.com/t/progressive-mode-understanding-ray-bundle-size/50357/2 "2014-07-03T10:07:56Z")

</div>

Get Slave monitor software like ReFaMo.

Then start DBR and adjust values untill all nodes run at 100%

The lower the CPU ray bundle size the faster it updates  
the bigger the CPU rays per pixel the more nodes will stay at 100% cpu

---

<div class="post-metadata">

**Author:** ![alexyork](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/alexyork/32/271382_2.png) [@alexyork](https://forums.chaos.com/u/alexyork)\
**Post date:** [July 3, 2014, 10:21am UTC](https://forums.chaos.com/t/progressive-mode-understanding-ray-bundle-size/50357/3 "2014-07-03T10:21:49Z")

</div>

> [@Dariusz\_Makowski\_Dadal](#):
>
> Get Slave monitor software like ReFaMo.
> 
> Then start DBR and adjust values untill all nodes run at 100%
> 
> The lower the CPU ray bundle size the faster it updates  
> the bigger the CPU rays per pixel the more nodes will stay at 100% cpu

Thanks - that all makes sense, and it’s what I’ve been doing for DBR renders, but what about for non-DBR renders? I feel like, logically, reducing that value should be better?

---

<div class="post-metadata">

**Author:** ![Dariusz\_Makowski\_Dadal](https://avatars.discourse-cdn.com/v4/letter/d/c4cdca/32.png) [@Dariusz\_Makowski\_Dadal](https://forums.chaos.com/u/Dariusz_Makowski_Dadal)\
**Post date:** [July 3, 2014, 10:31am UTC](https://forums.chaos.com/t/progressive-mode-understanding-ray-bundle-size/50357/4 "2014-07-03T10:31:34Z")

</div>

Well it really depends what you are doing with it I think. If you are doing shader/light tests I tend to put CPU ray bundle to something like 4 so I get as fast updates as my patience allowed me to wait… If I do more final render I let it increase as then I get more render power as each update of RT window is a sacrifice of render power.

---

<div class="post-metadata">

**Author:** ![vlado](https://avatars.discourse-cdn.com/v4/letter/v/779978/32.png) [@vlado](https://forums.chaos.com/u/vlado)\
**Post date:** [July 3, 2014, 5:54pm UTC](https://forums.chaos.com/t/progressive-mode-understanding-ray-bundle-size/50357/5 "2014-07-03T17:54:44Z")

</div>

It is very similar to the bucket size for the production renderer - it determines the size of the image chunk computed by each CPU thread. The same rules apply - smaller values might get you faster previews, but require more frequent communication between the master and the slaves. Larger values allow to utilize the CPUs on the render slaves better but may slow down the updates.

Best regards,  
Vlado

---

<div class="post-metadata">

**Author:** ![alexyork](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/alexyork/32/271382_2.png) [@alexyork](https://forums.chaos.com/u/alexyork)\
**Post date:** [July 3, 2014, 8:46pm UTC](https://forums.chaos.com/t/progressive-mode-understanding-ray-bundle-size/50357/6 "2014-07-03T20:46:44Z")

</div>

> [@vlado](#):
>
> It is very similar to the bucket size for the production renderer - it determines the size of the image chunk computed by each CPU thread. The same rules apply - smaller values might get you faster previews, but require more frequent communication between the master and the slaves. Larger values allow to utilize the CPUs on the render slaves better but may slow down the updates.
> 
> Best regards,  
> Vlado

Thanks Vlado - so my query about using only the local machine still stands - are we better off using sub-128 values in this case? Like 64 or 32? Or is 128 a kind of “sweet spot” for local renders?
