Any idea to reduce RAM used by worker?

[ivancarlosti]

I ma running pwpush with worker to clear expired files, but I noticed that the worker itself eats more RAM than pwpush
Please, there is any way to reduce the amount of RAM used by it, at least on idle state?

[pglombardo]

Hi @ivancarlosti - I just did a bit of investigation and unfortunately none that I see currently. This file controls the worker configuration - it already defaults to 1 worker.

What we can do is add jemalloc to the application but this needs to be baked into the container. That usually gives a ~30% memory savings. I added it on pwpush.com and the affect was dramatic.

I'll create a feature request and see if I can add this soon.

[pglombardo]

Side note: The worker system is solid_queue and there have been some discussions about memory usage. I didn't see anything that stood out as an immediate fix: https://github.com/rails/solid_queue/issues?q=is%3Aissue%20state%3Aopen%20memory

[pglombardo]

@ivancarlosti - I just released v1.51.9 that should reduce memory from 10-30%.

Before you deploy, could you take some before and after screenshots that I could use? That would be very much appreciated.

[ivancarlosti]

@ivancarlosti - I just released v1.51.9 that should reduce memory from 10-30%.

Before you deploy, could you take some before and after screenshots that I could use? That would be very much appreciated.

Will do that!

[ivancarlosti]

I am tested now running pwpush:1.53.0
tags pwpush:stable + pwpush-worker:stable consumes 501MB
tag pwpush:1.53.0 (with worker embedded) consumes 700MB :/

[pglombardo]

Yeah this will definitely not help memory consumption. It's a trade off between ease and consumption.

...but you can set PWP__NO_WORKER=true for the pwpush:1.53.0 container and keep your existing setup.

[pglombardo]

Hi @ivancarlosti - another memory footprint improvement in v1.53.7. FYI.

With the improvement and disabling the in-container background worker gets about ~205MB.

[ivancarlosti]

U r awesome!!! ❤️