Why is there not Concurrent ArrayList in java.util.concurrent package.
I think that the main reason is that is difficult to understand how you could code a general thread-safe array list(*) that doesn't have inherent concurrency bottlenecks.
The real point / value of classes like ConcurrentHashMap is not that they are thread-safe. It is that they are thread-safe without being a concurrency bottleneck. For instance ConcurrentHashMap avoids the bottlenecks by having different locks for different parts of the table, and by relaxing the semantics of the map iterators.
The problem with the "array list" family of data structures is that it not obvious how you can avoid the bottlenecks. Take the contains() operation for example. How can you avoid locking the entire list while you search for the element?
The other observation is that the Queue and Deque interfaces do have concurrent implementations (based on linked lists). These APIs are more limited than the List API, but it is the limitations that makes concurrent implementations possible; c.f. the List.contains(...) problem.
(* The CopyOnWriteArrayList class is an interesting case. It avoids the concurrency bottleneck on read-only operations such as get and contains, but it does this by doing a lot more work in mutating operations, and by modifying the visibility rules. Furthermore, the mutating operations lock the entire list, and are therefore a concurrency bottleneck. These properties mean that CopyOnWriteArrayList can't be called a general purpose concurrent list.)
Read full article from concurrency - Why is there not Concurrent ArrayList in java.util.concurrent package - Stack Overflow
No comments:
Post a Comment