26
Lightweight paperless-ngx alternative?
(feddit.de)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Sep 2023
26 points (96.4% liked)
Selfhosted
61877 readers
374 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
https://awesome-selfhosted.net/tags/document-management.html#paperless-ngx
I stopped using Paperless-NGX for this reason. It eats RAM and CPU insanely even after configuring it to stop doing OCR and no ML. I wish there is a Go alternative.
Exactly what I was wishing for. Or Rust. Don't care. At least something that doesn't eat resources for breakfast.
I actually contemplated starting such a thing. But before I dive into another project I likely don't finish, I was hoping for something out-of-the-box.
Wasn't this reported as a bug on their repo? Does anyone know why is it eating such an amount of ram? It might be that this can be fixed.
I think all the RAM related issues were closed a while back and were supposedly fixed. I just don't understand why when interfacing with the front-end, it uses so much it would get OOM kill itself with 1.5 GB allocated memory.
Every page, as well as loading in the initial dashboard from an idle state, spikes the RAM. Are there no clever lazyloading happening or something? Surely viewing and modifying database entries can't be this memory intensive?
Maybe it's just an unoptimized Python thing. I stopped self-hosting stuff written in Python, with the exception of Linkding (which takes a while to also submit a link) and Whoogle.