Summary

You now see that the garbage collector task is not all that easy, but it certainly does a very good job managing memory automatically. You can help it a lot, especially if you are writing applications with performance in mind. Preventing the GC old space from growing is necessary to avoid long GC cycles. Otherwise, it can pause your application and sometimes force your services to restart. Every time you create a new variable, you allocate memory and inch closer to a new GC cycle. Even after understanding how memory is managed, you sometimes need to inspect your memory usage behavior. The cleanest way is by collecting snapshot heaps of the memory stack and analyzing using the V8 inspector or other similar pieces of software. The interface is self-explanatory, and leaks will show up simply if you sort the object list by shallow size, retained size, or reference counting. But before creating an application with a huge memory footprint, take a look at databases, whether relational...