Re:Java Memory Model Pragmatics
by fiatmoney on Saturday July 12, 2014 @01:12AM
(#8023770)
The memory model is actually relatively straightforward on the user side; it's significantly more complicated on the implementer side.
In most cases you can get away with coarser constructs (which are higher-performing anyway, eg task parallelism vs. trying to decompose an individual operation) and only dive into the language lawyering semantics when you, eg, really really need a lockfree concurrent linked list.
In most cases you can get away with coarser constructs (which are higher-performing anyway, eg task parallelism vs. trying to decompose an individual operation) and only dive into the language lawyering semantics when you, eg, really really need a lockfree concurrent linked list.