Especially since the move to Ruby 4, we have seen memory used by the engine on production steadily rising.
This usually indicates memory leaks or bad garbage collection.
We currently have enough memory on the server that this is not an urgent problem. Also, on the 4 week deploy date, the memory gets reset.
However, if we would release a new stable version, this reset will never happen, as stable versions never get deployed again, and containers not restarted. Before we release a new stable version, this issue needs to be tackled.
Especially since the move to Ruby 4, we have seen memory used by the engine on production steadily rising.
This usually indicates memory leaks or bad garbage collection.
We currently have enough memory on the server that this is not an urgent problem. Also, on the 4 week deploy date, the memory gets reset.
However, if we would release a new stable version, this reset will never happen, as stable versions never get deployed again, and containers not restarted. Before we release a new stable version, this issue needs to be tackled.