From fdeaa0fb8a51688e9ad7f4df35c3f3d93b73d00a Mon Sep 17 00:00:00 2001 From: binhnguyennus Date: Sat, 26 May 2018 16:02:13 +0800 Subject: [PATCH] Debugging Java Memory Leaks at Allegro --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index bd02133..11bcb5a 100644 --- a/README.md +++ b/README.md @@ -497,6 +497,7 @@ An updated and curated list of selected readings to illustrate best practices in * [Python Garbage Collection for Dropping 50% Memory Growth Per Request at Instagram](https://instagram-engineering.com/copy-on-write-friendly-python-garbage-collection-ad6ed5233ddf) * [Performance Impact of Removing Out of Band Garbage Collector (OOBGC) at Github](https://githubengineering.com/removing-oobgc/) * [Using Java Large Heap (110 GB) at Expedia](https://techblog.expedia.com/2015/09/25/solving-problems-with-very-large-java-heaps/) + * [Debugging Java Memory Leaks at Allegro](https://allegro.tech/2018/05/a-comedy-of-errors-debugging-java-memory-leaks.html) * [Optimizing JVM at Alibaba](https://www.youtube.com/watch?v=X4tmr3nhZRg) * [Performance Optimization on Video, Image, Page Load](https://developers.google.com/web/fundamentals/performance/why-performance-matters/) * [Optimizing 360 Photos at Scale at Facebook](https://code.facebook.com/posts/129055711052260/optimizing-360-photos-at-scale/)