I'm trying to show the higher ups that our codebase is not using objects correctly. We're making copies of immutable objects all over the place and its driving me mad. However, I have no 'proof' (i.e.

To reduce application execution time, Java’s segmented code cache would be extended with an optional “hot” code heap to compactly accommodate a part of non-profiled methods, under a draft JDK ...

An Oracle-developed, low-latency Java garbage collector geared to large heaps could move to the open source community, if a proposal to do so gets community approval. Votes are due by November 8.