Change Details

On a 4 million vertex mesh I observed a speed-up from about 30ms to about 20ms. I had hoped for better, but I think this needs more testing anyway.

This replaces the single-threaded calculation of mesh min and max positions with a `parallel_reduce` loop. Since the bounding box of a mesh is retrieved quite often (at the end of each evaluation, currently 2(?!) times when leaving edit mode, etc.), this makes for a quite noticeable speedup actually. On my Ryzen 3700x and a 4.2 million vertex mesh, I observed a 4.4x performance increase, from 14 ms to 4.4 ms. I added some methods to `float3` so they would be inlined, but they're also a nice addition, since they're used often anyway. --- If this is accepted, I'll look into updating the bounding boxes for some other object types, mesh needs a special implementation because `MVert != float3` [[ https://developer.blender.org/T93602 | yet ]] though ;).

On a 4 million vertex mesh I observed a speed-up from aboutThis replaces the single-threaded calculation of mesh min and max 30ms to about 20ms. I had hoped for better,positions with a `parallel_reduce` loop. but I think thisSince the bounding box needs more testing anywayof a mesh is retrieved quite often (at the end of each evaluation, currently 2(?!) times when leaving edit mode, etc.), this makes for a quite noticeable speedup actually. On my Ryzen 3700x and a 4.2 million vertex mesh, I observed a 4.4x performance increase, from 14 ms to 4.4 ms. I added some methods to `float3` so they would be inlined, but they're also a nice addition, since they're used often anyway. --- If this is accepted, I'll look into updating the bounding boxes for some other object types, mesh needs a special implementation because `MVert != float3` [[ https://developer.blender.org/T93602 | yet ]] though ;).