News for hackers. Stuff that matters.

A comment on Hard-won lessons: Five years with Node.js. Parent comment

Re:Hard-won lessons: Five years with Node.js by chrisco255 on Thursday April 20, 2017 @03:47AM (#14154720)
Your typical Node instance is using an order of magnitude less memory than the beastly JVM. We use Java microservices with Spring at my job and each "micro" service consumes close to 1GB of memory. I've never written a Node service that had more than 100MB footprint.
[ Parent | on HN ]
Re:Hard-won lessons: Five years with Node.js by empthought on Thursday April 20, 2017 @07:53AM (#14155822)
The default maximum heap size for the JVM on systems with 4GB or more of RAM is one gigabyte. Has this been changed in your microservices' startup parameters? If not, it is no surprise that Java uses the memory that you have allocated to it before garbage collecting.

Spring Boot microservices that don't do much shouldn't need more than 32MB heap -- see https://spring.io/blog/2015/12/10/spring-boot-memory-perform... for details.

[ Parent | on HN ]
Re:Hard-won lessons: Five years with Node.js by lod723 on Wednesday April 26, 2017 @10:57AM (#14203505)
The JVM has the same global heap problem as Node... it's frustrating that with all the development that goes into the JVM this problem remains unaddressed.
[ Parent | on HN ]