RAM consumption

[FredPraca]

Since the version 7, it seems that RAM consumption grew.
When uploading three photos of about 8Mb, php-fpm RAM rises to about 250Mb and more.
On my 2Gb RAM VM, uploading few photos consumes a lot of RAM and php-fpm gets killed.

Were there changes in the way photo handling that would explain this ?

[ildyria]

Hi @FredPraca
What setup are you using? docker compose or directly zip or clone and composer?

The zip/clone+composer should not have impact.
The main difference between version 6 and version 7 is on the new docker images with frankenphp (those the old php-fpm setup is still available with -legacy tag.

We also switch to jobs instead of direct processing. This allows you to have queue workers in the background dealing with the processing of images. It might be possible that the image is kept in memory at different stages and not cleared :| Though 250 Mb is a lot. :|

[FredPraca]

Hi @ildyria ,
I use the standard clone+composer install so the change with Docker image shouldn't have any impact.

But the switch to jobs seems to be the ideal culprit :)
I'll try to investigate to find when it appears.
As a first clue, on the webpage, the state is still "Uploading" when the php-fpm processes grow in memory.

[FredPraca]

WTF. Because that part was pretty much not refactored with the v7 and using the -legacy should produce the same results as on v6 etc.

Let's give it a try again, I may have done something wrong.
When using the legacy image, /conf directory has to be mounted. What is it supposed to contain ?

[ildyria]

When using the legacy image, /conf directory has to be mounted. What is it supposed to contain ?

your .env file which in the v7 can be ignored because all the env variables are directly loaded (as long as the .env values are in your docker container environment obviously).

I'm not even sure it is very necessary but I would need to dive because I have not used that side for more than 7 months now.

[FredPraca]

For your information, I've been using v7.7.1-legacy image as my database has already been migrated.

[ildyria]

I figured, I made sure that the -legacy and non -legacy images are supposed to be inter-changeables so that if frankenphp is broken for some reason there is a fallback. :)

[FredPraca]

So I confirm that when using v7.7.1-legacy image, 4 php-fpm processes out of 5 are climbing to 250Mb so the result is the same when using source code installation as I've done first, podman installation using FrankenPHP or php-fpm.
The main différence is that with FrankenPHP I have just one process eating a lot of RAM while with php-fpm I get 4 processes eating it.
Integration does not seem to be the problem so I'll try investigating by instrumenting code and find where RAM might be an issue.