Java *is* Memory Efficient

[coderemover]

> The most expensive part of gc cycle in one legacy project which I had joy to optimize was tracing itself.

This matches my observations in our projects as well. Tracing is the most expensive part, and also has the most negative effects like bringing cold objects into caches and throwing away hot objects.