forked from bartvdbraak/blender
064caae7b2
Several ideas here:
- Optimize calculation of near_{x,y,z} in a way that does not require
3 if() statements per update, which avoids negative effect of wrong
branch prediction.
- Optimization of direction clamping for BVH.
- Optimization of point/direction transform.
Brings ~1.5% speedup again depending on a scene (unfortunately, this
speedup can't be sum across all previous commits because speedup of
each of the changes varies from scene to scene, but it still seems to
be nice solid speedup of few percent on Linux and bigger speedup was
reported on Windows).
Once again ,thanks Maxym for inspiration!
Still TODO: We have multiple places where we need to calculate near
x,y,z indices in BVH, for now it's only done for main BVH traversal.
Will try to move this calculation to an utility function and see if
that can be easily re-used across all the BVH flavors.
|
||
|---|---|---|
| .. | ||
| bvh_nodes.h | ||
| bvh_shadow_all.h | ||
| bvh_subsurface.h | ||
| bvh_traversal.h | ||
| bvh_types.h | ||
| bvh_volume_all.h | ||
| bvh_volume.h | ||
| bvh.h | ||
| qbvh_nodes.h | ||
| qbvh_shadow_all.h | ||
| qbvh_subsurface.h | ||
| qbvh_traversal.h | ||
| qbvh_volume_all.h | ||
| qbvh_volume.h | ||