Open mkitti opened 1 month ago
The C++ api surface is quite large, however, generally speaking, tensorstore is designed to be thread-compatible at the c++ object level. So, unless otherwise marked, it's best to partition or guard tensorstore object uses when working with threads.
See, for example, the Abseil blog post on C++ types: https://abseil.io/blog/20180531-regular-types
All const
methods are thread-safe, non-const
methods are not thread safe.
All const
uses of a TensorStore
object (which is almost all uses) are thread-safe, for example.
Most objects in TensorStore are internally reference counted and use thread-safe copy-on-write internally where needed.
Is the the C++ API thread safe? Are there any considerations when calling tensorstore from multiple threads?