permaculture playing cards
The moose likes Java in General and the fly likes Concurrency API Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Java in General
Bookmark "Concurrency API" Watch "Concurrency API" New topic

Concurrency API

Anselm Paulinus
Ranch Hand

Joined: Sep 05, 2003
Posts: 390
During the course of learning the new API; I undestood that the new java.util.CopyOnWriteArrayList creates a new copy of the underlying array for writing thereby disposing off synchronization. My question is how does this affect memory management in a situation where there are many concurrent writes to be done; I guess it is going to create this many copies of the arrays and have them stored in memory; this I think is akin to having too many objects in a servlet session. Please correct me if I am wrong.
Henry Wong

Joined: Sep 28, 2004
Posts: 20531

I believe the CopyOnWriteArrayList only makes a copy to avoid stepping on an iterator. And once you make a copy, that iterator is safe from future writes. So the only scenario where lots of copies are made, is when you are getting lots of iterators while making lots of calls to mutable methods.


Books: Java Threads, 3rd Edition, Jini in a Nutshell, and Java Gems (contributor)
Anselm Paulinus
Ranch Hand

Joined: Sep 05, 2003
Posts: 390
Thanks Henry for the response
I agree. Here's the link:
subject: Concurrency API
It's not a secret anymore!