use std::vector<atomic > or concurrent_vector?

use std::vector or concurrent_vector?

If I have a vector that will be accessed by multiple threads, no creation or destruction, or even grow size will happen during multi-threading. Which one should I choose, a std::vector of atomic type, or concurrent_vector?

In other words, only the overloaded [] will be used to update and then read function will be called.




publicaciones de 4 / 0 nuevos
Último envío
Para obtener más información sobre las optimizaciones del compilador, consulte el aviso sobre la optimización.
Imagen de Raf Schietekat

concurrent_vector allows concurrent growth and guarantees that elements, once allocated, will stay in place, but it does not change anything about how each of them is used, so a std::vector should suffice in your situation. Whether you want a vector of atomics depends on whether you would use an atomic if there were only a single element: if your algorithm can avoid races by separating the writing and the reading (including proper synchronisation), you don't need an atomic, otherwise you do, but consider carefully as this is not a common situation.

Thanks. But concurrent_vector does have thread-safe feature(lock) for access (like using [] ), right?

Imagen de Raf Schietekat

You can have a race on any particular element with tbb::concurrent_vector just as with std::vector.

Inicie sesión para dejar un comentario.