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.
You must log in or register to comment.
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.
deleted by creator
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”…
-
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.
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
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.
