Warp <war### [at] tagpovrayorg> wrote:
>   Also note that since the radiosity data tree is probably accessed millions
> of times per second (for both reading and writing), mutexing each access would
> be prohibitively slow, as mutexes (especially those provided by Boost) are
> very inefficient. Mutexes are only feasible for functions which are called
> relatively infrequently.

Of this issue I was aware, which is why I suggested to basically cache some
intended tree writes before paying the cost of locking.

If 100% reproducability of shots is an issue though, another approach is indeed
needed.

(BTW, why is Boost used if it is so slow?)

Post a reply to this message