[Bf-cycles] Cycles criteria to set the default CUDA computing device
dfelinto at gmail.com
Tue Jan 22 19:06:15 CET 2013
Thanks for the reply. I was wrapping up my tests before getting back to you:
> It seems strange though that these Tesla cards would have a timeout,
maybe it's very big, otherwise that could make rendering unreliable.
This cluster in particular allocates a few nodes for "interactive sessions"
and those are the only ones that have a "Display GPU". All the "real" nodes
are set as pure GPGPU nodes.
In other words, for the "rendering" nodes in this cluster, to set CUDA as
the computation device is enough (the three GPUs are used in computation
automatically). For the interactive session however, the user needs to set
it manually (i.e. python), in order to get a reliable preview of the
(also for the records: a frame that takes me 180 minutes to render in a
good MBP from 2011 takes only 21 minutes in one node in this cluster :)
2013/1/15 Brecht Van Lommel <brechtvanlommel at pandora.be>
> No, that's not really the right behavior. If all devices are display
> devices, we should really enable all of them by default. It seems
> strange though that these Tesla cards would have a timeout, maybe it's
> very big, otherwise that could make rendering unreliable.
> On Mon, Jan 14, 2013 at 11:26 PM, Dalai Felinto <dfelinto at gmail.com>
> > Hi Brecht,
> > You explained me about the CU_DEVICE_ATTRIBUTE_KERNEL_EXEC_TIMEOUT over
> > but I wanted to double-check if I got it right.
> > I have a system with three GPUs, all of them setup as "Display GPU".
> > In this case, should we have the CUDA_MULTI* as the automatic option if
> > set CUDA as device?
> > Or to have CUDA_0 as the default (as it is now) is the expected
> > The available computing devices:
> > ('Intel Xeon CPU', 'Tesla M2070', 'Tesla M2070', 'Tesla M2070', 'Tesla
> > (3x)')
> > (‘CUDA_0′, ‘CUDA_1′, ‘CUDA_2′, ‘CUDA_MULTI_2′)
> > And with this patch  I get the following info:
> >  http://www.pasteall.org/38837
> > *** Begin CUDA Debug
> > CUDA device 0 is a Display GPU
> > CUDA device 0 has "14"
> > CUDA device 1 is a Display GPU
> > CUDA device 1 has "14"
> > CUDA device 2 is a Display GPU
> > CUDA device 2 has "14"
> > *** End CUDA Debug
> > Is this the expected behaviour?
> > Thanks,
> > Dalai
> > blendernetwork.org/member/dalai-felinto
> > www.dalaifelinto.com
> > _______________________________________________
> > Bf-cycles mailing list
> > Bf-cycles at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-cycles
> Bf-cycles mailing list
> Bf-cycles at blender.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-cycles