Paperless-NGX using 12.9GB of RAM, is this right?!
reddit / selfhosted

----------------------------------------------------------------------
spaulli · 2023-11-03 02:52

Hey yall, so I've setup paperless-ngx yesterday in docker on unraid,
and I've got about 70 documents loaded and tagged, and its by far
using the most RAM in my system. Sitting at about 12.9GB, and if I
start editing files or tags, it spikes up another 3-4GB. This feels
HEAVY and I can't figure out if theres some setting I need to change.
I've got the number of workers set to 1, and threads set to 1.

Any advice would be appreciated.

----------------------------------------------------------------------
clintkev251 · 2023-11-03 03:06

Mine's sitting at just under 500 MB, with a few hundred documents, and
no effort to optimize it. So I'd say you have some issues

----------------------------------------------------------------------
Couch941 · 2023-11-03 09:29

>I've got the number of workers set to 1, and threads set to 1.

What happens when you increase that?

----------------------------------------------------------------------
FayeInMay · 2023-11-03 09:43

I have the same issue and it seems like it is a memory leak, but the
devs said it's not on GitHub, so I don't even know.

----------------------------------------------------------------------
j0hnp0s · 2023-11-03 10:09

If I remember correctly, for me, it is tika that spreads itself after
uploading files.

It's easier to troubleshoot if you are not using the omnibus
container, since you can more easily check resource consumption

----------------------------------------------------------------------
Tecchie088 · 2023-11-03 12:36

I've seen the same about 2 weeks ago, simple restart of the container
solved it.

There's probably a memory leak somewhere. See [closed GitHub
issue](https://github.com/paperless-ngx/paperless-ngx/issues/3616).

----------------------------------------------------------------------
botterway · 2023-11-04 08:27

I killed paperless because it kept doing this to my system. I wish
there was a better alternative.

----------------------------------------------------------------------
Throwaway-23842 · 2023-11-05 02:57

Maybe won't help your case, but have you tried setting a hard and soft
limit for the max number of file descriptors for the container? I had
what sounds like a similar problem but with a version of MySQL
([related issue on github](https://github.com/docker-
library/mysql/issues/579)). Apparently a combination of a memory leak
with a max number of open files to large for my pc to handle.
If you are using docker compose, you could set the limits for nofile
and even max number of processes like this:

`ulimits:`
`nproc: 65535`
`nofile:`
`soft: 20000`
`hard: 40000`

When I did this for my MySQL 5.7 image the memory usage fell from 16GB
(half my system´'s memory) to around 220MB. I know it is a completely
different containerized application, but I think it might be worth a
shot to try this.