No, cache lookup.
There is a reason why they are all CPU renders.
No, cache lookup.
There is a reason why they are all CPU renders.
CPU doesn't automatically mean Slow (It is not easy to beat corona render on comparable hardware even for Luxcore and Vray wich are GPU capable).There is a reason why they are all CPU renders.
Luxcore is fast really fast a real pleasure. For the same reason it is frustrating to loose all that speed in a lot of scenario cases. And when you force to stay on speed you have to deal with flickering.Animation with moving object
Animation with animated light ( color / position)
Still or animation with mostly reflective surface
It is a lot of scenario cases where we miss the speed bump
Provided by PGI.
Next event estimation plus Cos MIS https://www.maurocomi.com/monteCarloPathTracer.htmlThe idea of next‐event estimation(NEE) or shadow rays is, to reuse the same path sample to sample light transport for different bounces. This is done by drawing explicit connections from every path vertex to the light source. This technique is very popular due to the performance improvements it brings.
It seem a bit common as even cycles already use it. probably it is already implemented inside Luxcore and i'm loosing time searching arround itCycles uses path tracing with next event estimation, which is not good at rendering all types of light effects, like caustics, but has the advantage of being able to render more detailed and larger scenes compared to some other rendering algorithms. This is because we do not need to store, for example, a photon map in memory, and because we can keep rays relatively coherent to use an on-demand image cache, compared to e.g. bidirectional path tracing.
So thank you very much for stopping this hemorrhage Doctor
Sharlybg wrote: ↑Wed Sep 02, 2020 12:10 pm I'm back again . There are been some nice improvement recently in the GPU compute area and memory bandwidth.
PCIe 4.0
And more recently nvidia RTX IO.
As for pratical path guiding technic the data transfert from CPU memory to GPU memory plus frequent communication was the bottleneck nullifying all sort of speed up I am wondering if theses 2 news improvement change something.
I'm no expert, but my understanding was that this is about uncompressing textures for example straight in gpu memory so that they don't have to do that in system ram and then load to gpu vram.FarbigeWelt wrote: ↑Thu Sep 03, 2020 8:17 amSharlybg wrote: ↑Wed Sep 02, 2020 12:10 pm I'm back again . There are been some nice improvement recently in the GPU compute area and memory bandwidth.
PCIe 4.0
And more recently nvidia RTX IO.
As for pratical path guiding technic the data transfert from CPU memory to GPU memory plus frequent communication was the bottleneck nullifying all sort of speed up I am wondering if theses 2 news improvement change something.
AMD Radeon 5700 XT
GPU Memory Memory Speed (Effective)
14 Gbps
Max Memory Size
8 GB
Memory Type (GPU)
GDDR6
Memory Interface
256-bit
Max. Memory Bandwidth
448 GB/s (<- 14 Gbit/s / 8 bit * 1 byte * 256)
On nvidia‘s graphic transfer rate from RAM to VRAM is 14 GB/s. This is 32 times less than VRAM to GPU cache.
The slide is about CPU/SSD/etc. (any device attached to the PCIe bus) to GPU ram transfer rate. It can have a huge impact on some application.FarbigeWelt wrote: ↑Thu Sep 03, 2020 8:17 am On nvidia‘s graphic transfer rate from RAM to VRAM is 14 GB/s. This is 32 times less than VRAM to GPU cache.