OOM errors despite having raised memory allocation

I’m seeing regular OOM log messages with low RSS values despite having set my VM limit to 2GB on a dedicated-cpu-1x.

2021-04-23T16:35:12.550Z 70c2bf82 ams [info] [54292.250480] Out of memory: Killed process 665 (bundle) total-vm:331888kB, anon-rss:144220kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:608kB oom_score_adj:0

I’m also confused about what the fly scale memory command does since it appears to only allow setting to the full memory size of the VM:

$ fly scale memory 1024
Error 1024mb is less than the base memory 2048mb of dedicated-cpu-1x.

There was an issue applying the larger VM size to your app so it’s still using the 256mb ones. I’ll let you know when it’s fixed, should be a few minutes.

You’re right, changing memory sets the total VM memory, not additional. I wrote that command and it still confused me when I tried it yesterday. We’ll need to clean it up.

Cool, thanks! I will try to optimize this app with jemalloc to see if it fits in 256MB, but it’s Rails…

Looks like the right VM size was applied in the last deploy. Is it working better?

I haven’t seen any new errors yet. Is there a way to see what you’re seeing using flyctl?

We don’t have metrics in flyctl but you can see them in the ui: http://fly.io/apps/app-name/metrics