Intel® oneAPI Threading Building Blocks
Ask questions and share information about adding parallelism to your applications when using this threading library.
Announcements
The Intel sign-in experience has changed to support enhanced security controls. If you sign in, click here for more information.
2452 Discussions

use std::vector<atomic > or concurrent_vector?

missing__zlw
Beginner
724 Views

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.

 

Thanks

 

0 Kudos
3 Replies
RafSchietekat
Black Belt
724 Views

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.

missing__zlw
Beginner
723 Views

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

RafSchietekat
Black Belt
725 Views

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

Reply