It's probably going to be ok to scope them out and experiment a bit, but I doubt you'll get enough performance and stability to run it as production. Paperless' OCR is quite heavy on the CPU - iirc you can disable it but then you lose half of what makes it useful, and Nextcloud also does some processing to files that are uploaded to it. Since you are not running pi-hole or other latency-sensitive services it will probably be fine, it will just get sluggish while it processes uploads.
Selfhosted
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- 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!
While paperless processing is indeed quite intensive, it's not like this is a latency-sensitive task. If it takes 5m to OCR a scan, so be it. That doesn't make it unusably slow.
What I meant is that overloading the CPU on a Raspberry running pi-hole will make the whole network misbehave and timeout, until DNS requests are able to be serviced again. But since they're not doing that it should be fine :)
It's there any way around this? I don't want my smart home applications to run sluggish. They need to have priority.
I would say not in a way that makes sense, there may be hacky workarounds like setting nice
priorities or messing around with scheduling, but there's no way around hardware limitations. The Pi's CPU, RAM, and IO bandwidth are what they are, and you need overhead to guarantee "snappiness"
Nextcloud will be slow. To be realistic is it always slow in all hardware.
Ive been running HA (in docker container) and NextCloud on rpi4 4gb and it was working fine, but after server upgrade (diy pc) nextcloud became much more snappy (wasnt my reason to upgrade). Not sure about paperless, but I had many more lightweight services along with HA and NC. Im also not heavy HA or NC user, just my 0.02
Same here. My old Pi 4, was running HA, Nextcloud, Ghost blog, websites, Jellyfin and a couple of other small things. It did it fine, but when I upgraded to the Odroid H3 it all became so much faster and snappier.
So I should look into hosting docket on my pi and upgrade as soon as I feel like it?
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
Fewer Letters | More Letters |
---|---|
DNS | Domain Name Service/System |
HA | Home Assistant automation software |
~ | High Availability |
NAS | Network-Attached Storage |
NUC | Next Unit of Computing brand of Intel small computers |
4 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.
[Thread #94 for this sub, first seen 31st Aug 2023, 10:15] [FAQ] [Full list] [Contact] [Source code]
Can always get a NUC or another Pi.