Re:Oracle Tunes Java's Internal String Representation
by dietrichepp on Wednesday December 25, 2013 @04:46PM
(#6964373)
What?
Java's strings are immutable, so copy-on-write is nonsense.
Performance tuning for mutable string types has been moving away from the copy-on-write paradigm (it used to be common in C++, but not any more). It's a big mess because the design of the C++ string class was truly botched, it's much less of a mess in other languages where you have different types for mutable and immutable strings (Java, C#, Python, etc.)
Java's strings are immutable, so copy-on-write is nonsense.
Performance tuning for mutable string types has been moving away from the copy-on-write paradigm (it used to be common in C++, but not any more). It's a big mess because the design of the C++ string class was truly botched, it's much less of a mess in other languages where you have different types for mutable and immutable strings (Java, C#, Python, etc.)