You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when the backend exports a Lift file, it:
Generates a zip file temporarily on disk (can be many 100s of MB)
It reads this into memory
It base64 decodes the contents in memory (which expands it ~30%)
It sends this to the client in an HTTP response
This leads to peak memory usage of about (export_size x 2.3). It has been observed that for a 600MB export, system memory utilization increased to 2.2GB.
One option is to use NGINX sendfile to allow NGINX to efficiently stream the file back to the client and not load it into the backend memory:
Currently when the backend exports a Lift file, it:
This leads to peak memory usage of about (export_size x 2.3). It has been observed that for a 600MB export, system memory utilization increased to 2.2GB.
One option is to use NGINX
sendfile
to allow NGINX to efficiently stream the file back to the client and not load it into the backend memory:The text was updated successfully, but these errors were encountered: