Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce...
by nine_k on Tuesday December 24, 2019 @04:37PM
(#21875072)
At one of my recent employers, we wondered why some of our services consume whopping 200 MB when a normal service would run on 50 MB. A service requiring 1-2 GB would be considered a behemoth.
Unless your code is extremely complicated, or you are running a Jack-of-all-trades monolith, the only way to reasonably consume gobs of RAM is to keep an in-memory database / cache. This trades RAM consumption for speed. This is what e.g. IntelliJ does.
Running a heap larger than you need slows you down in the long term, because GC over a large heap consumes more time and CPU.
Unless your code is extremely complicated, or you are running a Jack-of-all-trades monolith, the only way to reasonably consume gobs of RAM is to keep an in-memory database / cache. This trades RAM consumption for speed. This is what e.g. IntelliJ does.
Running a heap larger than you need slows you down in the long term, because GC over a large heap consumes more time and CPU.