Replies: 4 comments 4 replies
|
Did a bit more digging.. When stopping code-server container, I face enough free memory to run paperless-ngx? Paperless seems to allocate twice the memory of e.g. Home Assistent. 500mb in my case. Has anybody experience on this matter? Could I limit the memory assignment when starting the container so that paperless would still run responsive? I dont require paperless to be fast in processing. There is only a demand for a few documents every now and then in a private house hold |
|
2GB of memory is quite low, but paperless is capable of running on a Raspberry Pi. I would suggest looking through: https://docs.paperless-ngx.com/setup/#less-powerful-devices |
|
This discussion has been automatically closed due to inactivity. Please see our contributing guidelines for more details. |
|
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
could you help me with expected system requirements for paperless-ngx? I understood that for casual use a Raspberry should be fine for paperlessNGX? I'm trying to run it on my Synology NAS DSM423+ (Intel Celeron J4125, 4 Cores, 2.0 each; 2 GB Memory) which outperforms a raspbery 4 by roughly 250%.
Currently running a few smaller containers and HomeAssistant, which usually remains low at 2-3% CPU but might jump to 30% for a few seconds every now end then..

After installing via portainer/docker (configured to run with redis/postgres and 2 languages for PAPERLESS_OCR_LANGUAGE) the entire NAS becomes unresponsive. I can't SSH; cant use the web interface of any docker container or DSM (Synology OS). After few hours, it seems the paperlessngx webserver container gets killed. Logs show:
This might be memory related. Not sure.. Any advice?
edit:

just found these issues thx to Glance which shifts my focus back to the CPU?
according to the paperlesss documentation, I might do wrong here, as I configure 2 OCR languages?
https://docs.paperless-ngx.com/configuration/
"This can be a combination of multiple languages such as deu+eng, in which case Tesseract will use whatever language matches best. Keep in mind that Tesseract uses much more CPU time with multiple languages enabled."
Thank you in advance
All reactions