My Nextcloud has always been sluggish — navigating and interacting isn’t snappy/responsive, changing between apps is very slow, loading tasks is horrible, etc. I’m curious what the experience is like for other people. I’d also be curious to know how you have your Nextcloud set up (install method, server hardware, any other relevent special configs, etc.). Mine is essentially just a default install of Nextcloud Snap.
Edit (2024-03-03T09:00Z): I should clarify that I am specifically talking about the web interface and not general file sync capabilites. Specifically, I notice the sluggishness the most when interacting with the calendar, and tasks.
deleted by creator
@Kalcifer @selfhosted it’s quite slow for me. AIO docker setup
It was way worse when I tried the snap tho
As long as it’s faster than the snap, it’s worth it to me 😜
I’ve shit-talk NC so much on here and other forums but for some reason kept feeling compelled to try to make it work. I’ve tried a few of the Community Docker templates available on Unraid “store” as well as AIO. I’ve had issues with all of them. Then gave NextcloudPi a try on a spare Pi 4 (installed a SSD as boot instead of microSD) and it works much better. It’s still much slower than I think it should be, but this version is far and away more responsive than the others.
Seafile is a beast of an app that syncs and performs incredibly fast. Some folks won’t use it due to the git-like chunks it parses your data into on the server end (this is what accounts for the speed from what I’ve read). I understand the concerns in that regard, but I still like it and I have my own way to mitigate that concern.
I use it on cheap vps since ~4yrs and work “well” but I’ve never had a single major update that didn’t have an issue on my LXC/Alpine container 😒 One moment it’s the packages name that have changed, one time it’s PHP version, another it’s a config, another is a addon, last time that was opcache, … and I’m a bit tired of having to spend hours each time doing maintenance of it.
I really think I’m going to go back to something simpler but more solid like an SSHFS or similar.
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 Git Popular version control system, primarily for code HTTP Hypertext Transfer Protocol, the Web IP Internet Protocol LXC Linux Containers NUC Next Unit of Computing brand of Intel small computers RPi Raspberry Pi brand of SBC SBC Single-Board Computer SSD Solid State Drive mass storage VPN Virtual Private Network VPS Virtual Private Server (opposed to shared hosting) ZFS Solaris/Linux filesystem focusing on data integrity nginx Popular HTTP server
11 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.
[Thread #566 for this sub, first seen 3rd Mar 2024, 08:45] [FAQ] [Full list] [Contact] [Source code]
Mine has always been slow. I started on a raspberry pi but later on a NUC and even on my VPS at Hetzner, it was always like you describe. Because I only used it for calendar, adressbook and sharing a few files I replaced it with Radicale for CalDav and CardDav and Syncthing for sharing files.
Yeah, me too. Nextcloud is way too unwieldy for basic usage like calendar/contact/even file sync. I tried a couple collaboration tools but they only stuttered and crapped out.
I’m actually fine hosting several smaller, dedicated services for the features I need rather than one lumbering point of failure.
Spent a full day setting up Nextcloud so I could file sync my machines and share files externally. It was slow as hell and didn’t work half the time.
Spent 10 minutes spinning up Syncthing and FileBrowser containers and have had zero issues with them since.
Nextcloud pleases A LOT 10% of it’s users. Those 10% are composed by tech savvy people, coders and developpers that spent countless hours tinkering with their instance.
I’m one of the 90% left. Despite really wanting to use nextcloud and trying to set it up correctly for 2 years, I finally gave up and I feel much happier in my life, in my work, with my family and friends, and they thank me for that.
Now I just recommend Owncloud or seafile. They’re both really easy to install and just work out of the box.
Out of habit and convenience, I keep a nextcloud running on oracle free tier just for what it’s good at: caldav and contacts.
The out of the box experience of the containerized nextcloud is actually really bad. Had it running bare metal with apache and it was way faster.
But have you tried the official AIO docker compose file? Basically copy the redis stuff from there and you are good to go.
Containers run on “bare metal”.
Not in this context. Bare metal means all packages and services installed and running directly on the host, not through docker/lxc/vms
Yes - in this context containers run on bare metal. They run directly on the host. They even show up in the host’s process list with PIDs. There is no virtual machine between an executable running in a docker image and the CPU on the host.
Have you read my comment? It’s about where the packages and services are installed.
In this case, they’re installed in the container, not on the host
What is it you think the “metal” is in in the phrase “running on bare metal?”
Your comment is irrelevant. Who cares in what directory or disk image the packages are installed? If I run in a “chroot jail” am I not “running on bare metal?” What if I include a library in /opt/application/lib? Does it matter if the binaries are on an NFS share? This is all irrelevant.
The phrase means to be not running in any emulation. To answer my question above - the “metal” is the CPU (edit: and other hardware).
edit2: I mean - it’s the defining characteristic of containers that they execute on bare metal unlike VMs and (arguably - I won’t get into it) hypervisors. There is no hardware abstraction at all. They just run natively.
It’s just what it means in this specific context.
They’re not running directly on the host, with directly meaning directly.
If you go by definition, I agree with you, but the definition is not always the thing to go off of.
Never had an issue with mine. And running fine. Only thing I have done is use mariadb.
Now I just recommend Owncloud or seafile. They’re both really easy to install and just work out of the box.
Which one is lighter on your opinion?
Lighter, I dont know. Faster, I’d say owncloud. YMMV
Use the AIO. Its much faster than any other way I’ve had it set up and I’ve used NC for years. Easy to update, full featured, supported.
And anyone that tells you to use Own cloud instead doesn’t have a clue.
An issue I have with AIO is I can’t use an internal IP address, and I’m required to have a domain or revese proxy.
OwnCloud for now, NC for the manual install.
What do you mean no internal IP? I can access the instance on my local network via RPI address no problem.
EDIT: Realized I didn’t use AIO. Sorry.
Ooooh, I just checked and I am indeed not running the AIO. Must be a new thing, and I though I had it because I didn’t set up much, but I really just used a premare docker-compose.yml, which is why I didn’t remember any advanced setup. It still uses multiple containers.
I stand corrected.
mine was really sluggish for a long time, then I saw someone in here explaining their similar issue and their fix. I don’t have the post link, but it was related to DNS settings. Basically for some reason using my pihole dns made only nextcloud sluggish, the fix suggestion was to use 1.1.1.1, which worked. Now, it is a pretty fast nextcloud.
So on your Nextcloud server you use an external DNS and it greatly sped up you nextcloud? Because I noticed a few years back mine got slow and I cannot figure out why. It was about the time I enforced pihole dns with pfsense. I might need to try this.
Pretty sluggish for me as well. Bare metal install with Apache, PHP 8.3, since a few days PostgreSQL and the whole Redis memcached opcache whatevercache stuff. Next step would be to check if the AIO Docker is the magical thing that makes it fly.
Some 8 core CPU I’m too lazy to look up, 16 GB RAM and two HDDs. SSDs would probably help, I guess.
I run Nextcloud on an old laptop (i5-8500h) and tbh I find it super fast and responsive. I’ve barely done any tinkering or customization
I am very happy with mine and have only ever had one hiccup during updating that was due to my Dockerfile removing one dependency to many. I’ve run it bare metal (apache, mariadb) as well as containerized (derived custom image, traefik, mariadb). Both were okay in speed after applying all steps from the documentation.
Having the database on your fastest drive is definitely very important. Whenever I look at htop while making big copies or moves, it’s always mariadb that’s shuffling stuff around.
In my opinion there are 2 things that make nextcloud (appear) slow:
-
Managing the ton of metadata in the db that is used by nextcloud to provide the enhanced functionality
-
It is/was a webpage rendered mostly on the server.
The first issue is hard to tackle, because it is intrinsic and also has different optimums for different deployment scales. Optimizing databases is beyond my skillset and therefore I stick to the recommendations.
The second issue is slowly being worked around, because many applications on nextcloud now resemble SPAs, that are highly interactive and are rendered by your browser. That reduces page reloads and makes it feel more smooth.
All that said, I barely use the webinterface, because I rarely use the collaboration features. If I have to create a share I usually do that on the app because that’s where I send the link to people. Most of my usecase is just syncing files, calendars and contacts.
Containers run on “bare metal”…
-
Docker behind a Traefik proxy with crowdsec checking (adds additional lag). Ryzen 2700x 32GB local machine. All storage on SSD.
The web interface is very usable, switching subpages takes maybe half a second max without it being cached by the browser.
Could of course be quicker (as basically everything ever), but as we mostly use it with the Windows sync clients and Android apps we never really have any issues.
Which docker image do you use? AIO?
I stopped using it because it has an extremely complex protocol, with very large bloat that increases with the number of files, and incredibly sensitive to latency.
When I stopped syncing directories because they would take days to upload and started compressing them so they would finish in 10 minutes, I decided it had to go. (Oh, and it’s extremely sensitive to network problems too.)
I still use Nextcloud for syncing documents and other basic stuff that is relatively simple. But I started getting glacial sync times consuming large amounts of CPU and running into lots of conflicts as more and more got added. For higher performance, more demanding sync tasks involving huge numbers of files, large file sizes, and rapid changes, I’ve started using Syncthing and am much, much happier with it. Nextcloud sync seems to be sort of a jack of all trades, master of none, kind of thing. Whereas Syncthing is a one trick pony that does that trick very, very well.