[Bf-cycles] Bottleneck of gpu render

Matthew Heimlich matt.heimlich at gmail.com
Sat Mar 29 00:08:58 CET 2014


What do you mean by "process the model"? Currently models are
processed before exporting to the GPU, and they are then copied
completely into vRAM. All the GPU does is trace rays and calculate
shader ops, then display the result.

On Fri, Mar 28, 2014 at 6:50 PM, GeKo <geko.pua at gmail.com> wrote:
> But i really mean about the way that cycles process de model. I dont have
> any knowledge about raytracing render, but i am shocked about how the new
> hardware know improve so much rhe rendering, even when they have 5 time more
> cores.
>
> On 28 Mar 2014 23:11, "Brecht Van Lommel" <brechtvanlommel at pandora.be>
> wrote:
>>
>> There are various possibilities:
>>
>> * Memory and texture memory read/write bottlenecks
>> * Different Mhz for cores
>> * Different GPU architecture
>> * Not all cores occupied due to divergence or mismatched batch sizes
>> * CPU Overhead
>>
>> There's too many interacting parts to be sure without closely
>> investigating.
>>
>> Brecht.
>>
>> On Fri, Mar 28, 2014 at 9:30 PM, GeKo <geko.pua at gmail.com> wrote:
>> > Short question, Why the execution time don't decrease "linearly"
>> > according
>> > to the number of cuda cores?
>> >
>> > _______________________________________________
>> > 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
>> http://lists.blender.org/mailman/listinfo/bf-cycles
>
>
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> http://lists.blender.org/mailman/listinfo/bf-cycles
>


More information about the Bf-cycles mailing list