How responsive is your Nextcloud?
How responsive is your Nextcloud?
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're viewing a single thread.
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.
Is docker virtualized or otherwise emulating something? It's just a way to package things, like an installer? Then it's bare metal.
I had to look this up too, I thought docker containers were virtualized.
It’s just what it means in this specific context.
"I used the wrong words but I feel like justifying them as right."
This is that whole "I know literally means literally the opposite of what I meant but deal with it" bullshit. Whatever, I'll not argue with such lunacy. Words mean whatever you want them to.
Words evolve, and sometimes, they gain new meanings. "Bare metal" is not a scientific terms, and so it can be bent depending on the context.
You can either accept that or not, it doesn't change the fact that that's what it now can mean.
He look - I drive a car with a V8! I mean I know it only has 4 cylinders in-line but I count them twice and I like the letter "V" so in this specific context it's a V8!
It's all about where the packages and services are installed
No. Your packages and services could be on a network share on the other side of the world, but where they are run is what matters here. Processes are always loaded into, and run from main memory.
"Running on bare metal" refers to whether the CPU the process is being run on is emulated/virtualized (ex. via Intel VT-x) or not.
A VM uses virtualization to run an OS, and the processes are running within that OS, thus neither is running on bare metal. But the purpose of containers is to run them wherever your host OS is running. So if your host is on bare metal, then the container is too. You are not emulating or virtualizing any hardware.
Here's an article explaining the difference in more detail if needed.
More specifically, the container is run on bare metal if the host is running on bare metal. You are correct in this thread, not sure why you're being downvoted. I guess people don't know what virtualization technology is or when it is used.
If the nextcloud container is slow, it's for reasons other than virtualization.
not sure why you’re being downvoted.
LaNgUaGe EvOlVeS. 🙄
Wait what? I'm saying what you said is correct. Am I the one who's confused here?
Edit: oh maybe you meant that's the excuse people give for being wrong? lol
Yes, that's the excuse I've been getting. Sorry to be vague.
Never had an issue with mine. And running fine. Only thing I have done is use mariadb.
I just moved my files from nextcloud to seafile, founded that I don't really need chat, calendar, tasks and other things, only need to store files and have it synced between my devices.
Nextcloud works for my small company and I'm not going to change it for now.
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