Frugal memory management on the JVM (Meetup)
Last month the Microscope Meetup had Guillermo and yours truly on a (Frugal) Memory Management on the JVM talk.
We presented some ways to understand an application’s worload and detect when it may be indulging too much on your memory. Then discussed some common practises to reduce footprint and, when these are not enough other techniques to achieve zero-allocations on your fast path.
The recording is available at YouTube and here are the slides in PDF (the video is immutable, but let me know any errors in the slides).
Any thoughts? send me an email!
To get notifications for new posts, subscribe to my mailing list, the RSS feed or follow me on Twitter / Mastodon.
Archive
- Identifiers are better off without meaning
- Alert on symptoms, not causes
- How about we forget the concept of test types?
- How organisations cripple engineering teams with good intentions
- Migrating an Eureka-based microservice fleet to Kubernetes
- Talk write-up: "How to build a PaaS for 1500 engineers"
- Kubernetes made my latency 10x higher
- Sizing Kubernetes pods for JVM apps without fearing the OOM Killer
- GC forensics by example: multi-second pauses and allocation pressure
- How does the default hashCode() work?
- Frugal memory management on the JVM (Meetup)
- DirectBuffer creation / disposal has hidden contention on sun.misc.Cleaner