Go memory ballast: How I learnt to stop worrying and love the heap

Re:Go memory ballast: How I learnt to stop worrying and love... by senko on Monday December 02, 2019 @03:52AM (#21680893)

> the Visage application which runs on its own VM with 64GiB of physical memory, was GC’ing very frequently while only using ~400MiB of physical memory

Why would you provision a 64GB machine if you only need less than 1% of that?

Especially given earlier:

> One approach to handle this is to keep your fleet permanently over-scaled, but this is wasteful and expensive. To reduce this ever-increasing cost, [..]

This already was over-scaled.

[ Parent | on HN ]

Re:Go memory ballast: How I learnt to stop worrying and love... by jerf on Monday December 02, 2019 @08:17AM (#21682039)

There aren't any cloud instances of anything with 32 cores but only 4 GB of RAM. I've got some similarly lopsided systems, because I don't need the RAM.

Even if you physically deploy them, that would be a silly loadout. Take the bit of insurance out and stick some RAM in it. The cloud providers don't offer these instances because if you run the numbers they don't really make sense.

[ Parent | on HN ]