What is the RAM usage for this?
-
@scooke said in What is the RAM usage for this?:
Can someone share the RAM usage for OmekaS running in it's own container, versus running it in a LAMP container, please?
I didn't watch that and I have no more Omeka installation on LAMP
I increased the RAM default requirement to 50OMB because there may be some batch jobs or graphics processing, for example with the IIIF modules. Some modules also require packages that are not necessarily provided with the LAMP app (but I didn't check)
-
@jeau @scooke I have it in a test LAMP app with its default 256MB and now it’s indeed 500MB. I guess it’s good.
However if you check within the app Systeminformation it says:
Memory Limit 128M
POST Size Limit 64M
File Upload Limit 64MThe memory limit is only 128MB?
With only 64MB upload you can’t upload a video if needed, maybe it could be increased to 1GB?BTW @jeau you did a very good job with presenting and building this app!!
-
@imc67 these values are defined (by Omeka app Dockerfile) in
/etc/php/7.4/apache2/php.ini
and refer tomod_php
sessions for Apache.; Maximum amount of memory a script may consume (128MB) ; http://php.net/memory-limit memory_limit = 128M ; Maximum size of POST data that PHP will accept. ; Its value may be 0 to disable the limit. It is ignored if POST data reading ; is disabled through enable_post_data_reading. ; http://php.net/post-max-size post_max_size = 64M ; Maximum allowed size for uploaded files. ; http://php.net/upload-max-filesize upload_max_filesize = 64M
To upload large files, Omeka users prefer to use the FileSideload module.
-
@jeau said in What is the RAM usage for this?:
To upload large files, Omeka users prefer to use the FileSideload module.
O, ok, that’s a good learning, thanks!
-
@jeau For the PHP apps, we follow the customizable php.ini pattern. Line 26-29 basically. This way people can tweak those values as needed. One important thing to remember when packaging this way is that the app's WORKDIR has to be set to /app/code and not /app/data because apache behaves differently when it is started in a directory which has php.ini in it!