I’ve seen a lot of recommends for Immich on here, so I have an idea what the answer here is going to be, but I’m looking for some comparisons between it and Photoprism I’m currently using Synology Photos, and I think my biggest issue is it’s lack of metadata management. I’ve gotten around that with MetaImage and NeoFinder. I’m considering moving to something not tied to the Synology environment.
How many photos do you store there that you recommend it? Like 500? With any serious number of photos Nextcloud starts loading for minutes and the android app autoupload goes tits up.
That bug is open for years and if with so many users affected and a commercial entity behind this project nobody has fixed it yet, I doubt it’s fixable without a very major rewrite.
Such a good point. I’m honestly surprised people recommend Nextcloud so frequently. I’ve used it in a commercial environment and it sucks ass. It broke numerous times when upgrading, it was buggy and slow. At the time their GitHub page had like 4k open issues and another 8k closed. Looks like it’s somewhat better now. Many of issues we’ve experienced were reported but no movement for years. It’s like least stable OSS I had dealt with.
Exactly, same here. Nextcloud is the only container for which I disabled auto upgrades, because I don’t always have 8 hours to deal with the aftermath.
I asked someone about this a few days ago, and they claimed to have over 30000 photos in Nextcloud without issues
Probably using Nextcloud Memories. Its very performant.
Lucky bastard!
I’ve got something in the region of 80gb of jpeg and raw files.
Probably 8000-9000 photos.
Yeah syncing from my phone was a bear, but I just let it run overnight.
Also not using iOS for what it’s worth. iOS is a shithole when it comes to overaggressive battery optimisation.
It was around 10k-15k photos that the server stopped working well. I’m surprising syncing on Android worked well for you with 8k photos though, there are so many bug reports on Github with cases like mine where it just stops working with 2k photos. Not slow, but failing to sync at all.
What is this serious number you have in mind? I’m the first one thinking that some of the design choices behind nextcloud are laughable, and that their attitude towards code quality and best practices is inadequate, but even then I don’t think this threshold is easily reached.
Well. It just stopped working after the 2k items mark for me. Had to increase php memory and all for almost 6GB to make it work. Still sluggish AF. It’ll be just my file bucket for now on. EDIT: I will like to add, Immich is now with 32k assets for me, working flawlessly and only using 300MB when active of memory.
I am about 3 orders of magnitude beyond you in terms of content, and I host that on 2GB RAM and a CPU that scores 440 on CPU benchmark.net . You might want to check your configuration, perhaps starting from the database (I use PG), then server (php-fpm). I don’t even use redis for caching, just the basic APC.
Some people have luck like this and guess they’re the ones advocating. I first had a hand-installed instance with all the recommended optimizations like Redis, and then I started fresh with Docker + Redis. In both cases, after 10-15k files it was extremely slow. Both on server hardware with plenty of RAM.
To be totally fair, in my long history with it, I’ve been complaining more about the bad performance of nextcloud than the opposite (I still do), but things improved quite significantly after I moved (a long time ago) to postgresql+pgbouncer, which made it acceptable. Tuning did the rest.
There can be several reasons why your experience with nextcloud is not optimal. For instance, if you have a slow mechanical drive and a weak 2-cores CPU like I do, it’s enough to hit a large folder with many pictures for the first time to have it grind to a halt: the server will become IO and CPU starved while php-fpm fork bombs (on a default config) way too many imagemagick processes to render miniatures of the photos, which, when those are large, will make sure to eat the little amount of RAM you had left, further pushing you into swap and memory-compression territory, making things even worse IO & CPU-wise. This is easily mitigated by rendering the miniatures asynchronously via a cronjob and making sure that there is a reasonable limit to php-fpm’s parallelism to keep your app, navigation and overall system responsive.
Honestly, this is basic sysadmin/tuning stuff, that only you (with the knowledge of your hardware) can do right (and should do, the reward is immense). And it might very well be that nextcloud is (much) more demanding than other apps due to its inherently bad design & stack. It does the job, though, and isn’t afraid of taking hundreds of thousands of files.
I’ve got the cron job and used Postgres in my previous instance. Limiting fpm concurrency is good insight, Ihavee not done that.
But do you know what works without all that and loads instantly? Photoprism.
Fair. Like I wrote previously (either here or in another thread) it’s likely that most self-hosters would at some point consider nextcloud given how versatile it is, and then it pays-off to tune for your config. If you do without, good for ya!
Great to know! Something is really odd on my instance. The DB is definitely working well on its own, all the queries are returned quite fast from what I gather on the monitoring side. Probably something odd on the server side. I’m using redis for caching, it helps a bit as it comes down to a halt without redis.
Nothing reported in the admin screen listing out config tips and missing indexes?
Nope, all I have is the default phone region not set.
Interesting! It’s hard to continue without more details, and I’m not an expert anyway, but something definitely should be off with your configuration :)
Thanks for trying though! Appreciate it. I’m happy to use nextcloud just for regular files for now anyways.
Nextcloud Memories is very fast. Photos is indeed a nightmare.