diff options
author | Patrick Mours <pmours@nvidia.com> | 2019-12-05 21:17:01 +0300 |
---|---|---|
committer | Patrick Mours <pmours@nvidia.com> | 2019-12-09 16:32:12 +0300 |
commit | baeb11826b9fe5525db6dd05ba5271949079fc1e (patch) | |
tree | 9d646d69ef51c3fb1dab3d76798936160b1560f9 /source/blender/compositor/operations | |
parent | c9dc57be3ae59fac84b243f8bfdaddaa9b5e2f20 (diff) |
Cycles: Add OptiX acceleration structure compaction
This adds compaction support for OptiX acceleration structures, which reduces the device memory footprint in a post step after building. Depending on the scene this can reduce the amount of used device memory quite a bit and even improve performance (smaller acceleration structure improves cache usage). It's only enabled for background renders to make acceleration structure builds fast in viewport.
Also fixes a bug in the memory management for OptiX acceleration structures: These were held in a dynamic vector of 'device_memory' instances and used the mem_alloc/mem_free functions. However, those keep track of memory instances in the 'cuda_mem_map' via pointers to 'device_memory' (which works fine everywhere else since those are never copied/moved). But in the case of the vector, it may decide to reallocate at some point, which invalidates those pointers and would result in some nasty accesses to invalid memory. So it is not actually safe to move a 'device_memory' object and therefore this removes the move operator overloads again.
Reviewed By: brecht
Differential Revision: https://developer.blender.org/D6369
Diffstat (limited to 'source/blender/compositor/operations')
0 files changed, 0 insertions, 0 deletions