>Heaviest remaining stack trace that I’m digging into now: swift_allocObject. It’s always memory… Reminds me of Kirk Pepperdine's "The Trouble with Memory" tal

>Heaviest remaining stack trace that I’m digging into now: swift_allocObject. It’s always memory… Reminds me of Kirk Pepperdine's "The Trouble with Memory" talk: https://www.infoq.com/presentations/jvm-60-memory/ https://www.infoq.com/presentations/jvm-60-memory/ Quotes: "Reduced allocation rates from 1.8 gigabytes per second to zero. (...) TPS jumped from 400,000 to 25 million." "about 70% of all the applications I run into are bottlenecked by some sort of memory issue (...) not only are people bottlenecked on this issue, they don't actually realize it. They don't even see it. It's not even visible to them." Then he goes on to enumerate some popular Java frameworks, and says: "If you use any of these, then you're very likely in the 70% of people that are suffering from memory issues."