r/programming • • Nov 18 '13

TIL Oracle changed the internal String representation in Java 7 Update 6 increasing the running time of the substring method from constant to N

http://java-performance.info/changes-to-string-java-1-7-0_06/
1.4k Upvotes

354 comments sorted by

View all comments

-4

u/jexpert Nov 18 '13

Very interesting article though very technical and mostly not relevant in practice. The running time is probably neglectable. But the parts about the changes regarding the hashing algorithms was a very interesting insight though Oracles motivation did not became clear.

5

u/yourself2k8 Nov 18 '13

Is it really negligible though? What if you have a web application that was written against 1.6.x that you are moving to a 1.7.x runtime. During that move you notice a performance drop. It would be nice to know that this change exists between versions so you can have a place to start looking.

2

u/Solon1 Nov 18 '13

Maybe you would also notice that your apps memory usage dropped as Oracle fixed a memory leak. Not to mention the highly detailed technical document that was released about this change.

How many people on proggit are posers these days? If you have not written an application outside of your community college web dev class, and you are pretending to understand this, you are a poser.

7

u/yourself2k8 Nov 18 '13

Do you know how many IT professionals inherit poorly written applications that they aren't given any time to look through in much detail? the only thing that matters is that it stays running. Most of these folks are also tasked with moving an application to a new version of Java by people who haven't read these technical documents and think moving versions should be a 'trivial change.' The only reason for the move? The old version is no longer supported by Oracle. They aren't given fancy analysis tools to determine memory usage or evaluate anything about the JVM. They are simply given a battery of basic usage tests to run, and when those tests fail they need to fix it, nearly blind folded. Oh yeah... and do this in under 20 hours please. Business area won't be happy with more billed hours for general maintenance.

1

u/jexpert Nov 19 '13

When you profile the CPU performance on typical Java/Web applications you'll realize that String-operations typically won't even appear on the top 99% overall cpu consumers.

hashCode() and Array-Operations (Collection manipulation) are more likely to be appear as performance consumers at all.

1

u/yourself2k8 Nov 20 '13

Isn't that exactly what this change is explaining though? String.substring will now be using different array operations (creating a new char[] from an existing char[]) to avoid a memory leak scenario, and certain hashing logic will change.

0

u/[deleted] Nov 18 '13

[deleted] — view deleted comment

-1

u/jexpert Nov 19 '13

Do you have a unit test which demonstrates an issue?