You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of concurrent_queue relies on a native synchronization mechanism, i.e. lock the entire queue structure whenever it pushes or pops. This leads to limited scalability. There are much more efficient implementation for MPMC Queues (e.g. Dmitry's lock free implementation that relies purely on atomics).
Plan:
Rename concurrent_queue to synchronized_queue, which reflects the implementation more accurately.
Implement a more efficient bounded_mpmc_queue (MPMC means Multi-Producer-Multi-Consumer).
The current implementation of
concurrent_queue
relies on a native synchronization mechanism, i.e. lock the entire queue structure whenever it pushes or pops. This leads to limited scalability. There are much more efficient implementation for MPMC Queues (e.g. Dmitry's lock free implementation that relies purely on atomics).Plan:
concurrent_queue
tosynchronized_queue
, which reflects the implementation more accurately.bounded_mpmc_queue
(MPMC means Multi-Producer-Multi-Consumer).References:
The text was updated successfully, but these errors were encountered: