Fwd: [concurrency-interest] ConcurrentHashMap footprint and contention improvements

Chris Hegarty chris.hegarty at oracle.com
Wed Apr 13 15:58:10 UTC 2011


This change does appear worthwhile. We have a narrowing window of 
opportunity for JDK7. I spoke to Alan Bateman about this and we feel 
that if we could finalize the JDK7 changes by next Monday (that is, get 
them in for JDK7 b140), this would give us a reasonable time for them to 
soak before it gets harder to get changes into 7.

Do you think this is a reasonable time frame? Do you expect any more 
implementation changes than what you have today?


On 04/13/11 01:13 AM, Doug Lea wrote:
> Members of this list are also invited to check this out.
> I'm not sure if it will make Java7 schedule, but the
> improvements seem worthwhile given the increased
> use of ConcurrentHashMap inside the JDK (including
> multiple tables per class loader in JDK7.)
> -Doug
> -------- Original Message --------
> Subject: [concurrency-interest] ConcurrentHashMap footprint and
> contention improvements
> Date: Tue, 12 Apr 2011 20:07:17 -0400
> From: Doug Lea <dl at cs.oswego.edu>
> To: Concurrency-interest at cs.oswego.edu <Concurrency-interest at cs.oswego.edu>
> For years, we've known that ConcurrentHashMaps have initial
> footprints (over 1000 bytes using default constructor) that
> are too big for casual use. And that the best way to address
> this would be to use the Fences API to emulate "final field"
> memory model guarantees in the presence of lazy initialization.
> But we aren't releasing the Fences API. So I committed a version
> that instead uses Unsafe calls to essentially the same effect
> (reducing initial footprint to around 100 bytes, plus a few
> percent savings for large populated tables). Also, this
> version includes throughput improvements under contention
> (mainly by interleaving locking with probes, to absorb cache misses),
> which can double performance on big tables with many threads.
> While conceptually straightforward, these lead to many
> line-of-code changes.
> The main price paid for these improvements is a greater reliance
> of "volatile" vs "final" reads, which are essentially equivalent
> in cost on most machines, but can be more costly on ARM and POWER.
> Even on these though, the net effect should be positive.
> It would be helpful if members of this list could help check
> that this is so. The committed version is now
> in java.util.concurrent sources (at
> http://gee.cs.oswego.edu/dl/concurrency-interest/index.html)
> and can be run by getting jsr166.jar and using
> "java -Xbootclasspath/p:jsr166.jar" with any java7 build
> or binary (http://dlc.sun.com.edgesuite.net/jdk7/binaries/index.html).
> Also, as an alternative, I temporarily placed an unpackaged
> source version (with the class renamed "CHM")
> at http://gee.cs.oswego.edu/dl/wwwtmp/CHM.java
> You can compile and somehow run in any java6/7 JVM.
> While working on these changes, I also contemplated other
> more extensive redesigns, including Cliff Click's non-blocking
> version (http://sourceforge.net/projects/high-scale-lib/)
> which usually has better scalability with large numbers
> of threads solely using get and put, but not otherwise
> uniformly a better choice.
> -Doug
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest

More information about the core-libs-dev mailing list