Running fizzy on docker uses a lot of memory

[locilocisu]

Is anyone else seeing the same behavior where my fizzy docker container would just hold on to the memory it was allocated? It is only when I restart the container then the memory usage is reset.

[c00llin]

Same problem here. I've set a max on the container.

[monorkin]

Hey @locilocisu can you share how much memory your container is using?

[c00llin]

Extra data point from my side ;)
I've got my container capped at 768MB, but before I did that it was eating all memory of my NAS until it died. At that point it was around 1.5GB. I only have 60 cards in fizzy.

[locilocisu]

It was about what @c00llin here reports. I saw it was taking about 1GB plus of ram, and my fizzy was a brand new install, so not even a single card yet. It does not start taking 1GB right away, after several days running it goes up to that and that's when like @c00llin, I applied a max RAM limit on the docker compose config. But it looks like whenever it grabs the RAM, it never lets go, hence just the ever increasing usage.

[estevao]

That's because of Solid Queue. If you are running it for personal use and is ok with disabling it, set 'SOLID_QUEUE_IN_PUMA: "false"' in your docker compose file, or tweak Solid Queue accordingly for your needs... #2343

[estevao]

It's both mem and cpu actually. With Solid Queue I was getting ~30% cpu and 1/2gb+ mem utilization when idle. Without it, it's around 4% cpu and 250mb mem.

You have to recreate the container for the new env variable to work though:

docker compose down fizzy
docker compose up -d --force-recreate fizzy

[locilocisu]

Odd, indeed doesn't do anything for me and I tried fully recreating the container. With or without the setting, I never had issues with the CPU utilization. I'd have spikes of CPU usage, but never a sustained use.

[c00llin]

I tried the variable already as well. It did help, but still leaks, mem goes up more slowly. I also reduced the number of workers from 4 to 2 which also helped but only to postpone the issue. Wrt to CPU, it was taking about 20% of my CPU once the mem filled up.
I've shut it down until it's fixed, since it's draining my swap mem well. Unusable like this.

[estevao]

I was able to make is stable at ~650MB mem and ~4% cpu utilization (mini M1):

Configs:

 RAILS_ENV: "production"
 SOLID_QUEUE_IN_PUMA: "false"
 WEB_CONCURRENCY: 1
 RAILS_MAX_THREADS: 2
 MALLOC_ARENA_MAX: 2

What are you using?

[c00llin]

Now using:
- RAILS_ENV=production
- SOLID_QUEUE_IN_PUMA=false
- WEB_CONCURRENCY=2 #lower value here gives a warning in the log file
- RAILS_MAX_THREADS=2
- MALLOC_ARENA_MAX=2
With these settings mem usage gradually climbs without even using the app, only running the container. When then starting to use the app, mem goes up very high. I then didn't touch it for a while and it still went up until reaching max again. Pretty concerning how much leakage this app has even with a minimal number of workers and the solid queue disabled.