undefined

points

[-]

Seriously. I ran it on a server with two Xeon CPUs and 128GB of RAM. The web interface took minutes to do anything. Browsing a large photo library was just completely unworkable (and that was before they ripped out all the sorting and filtering features from the photo library).

My instance killed itself somehow, likely a failed auto update. I was, of course, using the default docker setup with the watchtower instance etc etc. I never got it to come back up, and I haven't missed it at all.

Even opening the damn login page took a good 30 seconds to load, there's no excuse for this kind of performance on a real-deal enterprise server.

by c0balt2 hours ago|

parent|

[-]

NextCloud needs tuning (mostly of php-fpm and caching ) oob to be fast/usable in my experience. Just throwing resources at it won't make it faster as the defaults are generally quite conservative.

They even have a specific guide for this topic, https://docs.nextcloud.com/server/stable/admin_manual/instal...

As a side note, it's PHP so your single core clocks will generally be more relevant for latency than multi-core performance, feeding many cores requires a lot of divisble work.

by esperent1 hours ago|

parent|

prev|

[-]

I run it on a Hetzner vps with 4 vcpus, 16gb of ram that's also running multiple other containers. I haven't checked recently but most of that ram is free.

I'm not going to claim nextcloud is the snappiest app but I can open it right now, from across the world from my server as I'm on vacation, and it loads in <5s. I haven't done much tuning.

by bityard1 hours ago|

parent|

prev|

[-]

I'm not sure how you are holding it, but I ran Nextcloud on a VPS with under 1GB RAM for many years, now it's on a 12GB RAM cloud instance and is only using a few GB of RAM last time I checked.