For what it's worth, we would welcome this change. We took a large memory hit and a small performance hit when we upgraded from 1.6 to 1.7 in some of our memory-bound applications.
>From a purely performance perspective, the most expensive CPU operations are >memory access these days. Anything that halves memory reads will likely >produce better performance. >From an implementation perspective, having used 1.6's compressed strings >feature in production, we are comfortable that none of our code, nor any of >our dependencies rely on String internal representation in such a way as to >cause a significant backward compatibility issue. Thanks Moh >-----Original Message----- >From: core-libs-dev [mailto:core-libs-dev-boun...@openjdk.java.net] On Behalf >Of mark.reinh...@oracle.com >Sent: Thursday, May 14, 2015 7:05 PM >To: xueming.s...@oracle.com >Cc: core-libs-dev@openjdk.java.net >Subject: JEP 254: Compact Strings > >New JEP Candidate: http://openjdk.java.net/jeps/254 > >- Mark
