Changes

Jump to: navigation, search

Team Darth Vector

54 bytes added, 13:44, 9 December 2017
m
Parallelism Problems & Convoying in STL
If we attempt to find the data in parallel with other operations ongoing, 1 thread could search for the data, but another could update the vector size during that time which causes problems with thread 1's search as the memory location may change should the vector need to grow(performs a deep copy to new memory).
Locks can solve the above issue but cause significant performance issues as the threads are forced to wait for each other. This performance hit is known as '''Lock Convoying'''.
[[File:DarthVector ThreadLock.PNG |thumb|center|400px| Performance issues inside STL]]
129
edits

Navigation menu