WPLA 2.x\\ BUG - Memory usage issues

[rflinnenbank]

Some users of (at least) the Gunicorn image encounter high memory usage when dealing with the AROME updating process and while requesting AROME data. This results in the update process requiring up to and at times over twelve gigabytes of memory, and the request parsing to even run out of memory even when only requesting a few megabytes.

Steps to reproduce the behavior:

1. Use Gunicorn image based on version 2.47.031.
2. Adjust lock-file to match that of the reporting party to duplicate exact container settings.
3. Verify occurrence of memory usage problems

Expected behavior When updating AROME data, the maximum memory usage should barely go above the size of the files being processed (400-500Mb for now) . The same goes for regular requests, which shouldn't generate any kind of issue under several gigabytes of data processing.

Additional context This issue is a strange one, because even in the image we install via poetry with a .lock file in the folder. This should normally mean that there aren't that many possible differences between different installations of the image. This makes one wonder even more about the reason for such huge differences in memory usage.