Selfhosted

"Way faster" came from me :D

It is the complete package which makes it way faster...

Postgres, Redis, PHP Opcache, general PHP tweaks ( PHP.ini, child processes etc, use calculator ), HTTP-2 instead of 1.1

For HTTP-2, you can add this for Apache in your vhost:

Protocols h2 h2c http/1.1

For example:

<VirtualHost *.80>
ServerAdmin admin@server.com
DocumentRoot /var/www/html/nextcloud/
ServerName my.domai.com
Protocols h2 h2c http/1.1

....

In NGNIX add this in a new line:

http2 on;

For example:

server {
  listen 80;
  listen [::]:80;
  server_name my.domain.com;
  http2 on;

....

Using NGINX over Apache did nothing for me, so I use Apache with PHP-FPM 8.3, because I am using it for Wordpress too, same for Redissockets. I would recommend not to use a docker container for Nextcloud. I don't like it for Nextcloud and I don't use docker for Wordpress. Docker has other use cases in my setup, but not those 2.

This is just my personal setup.

Maybe it can help someone :)

Try MySQL instead of MariaDB. They have some performance tweaks in version 10 that aren't present in MariaDB.

Also, tune your MySQL (or MariaDB) server. Make sure all tables use InnoDB. Enable the slow query log and analyze slow queries (there may be missing indices). If there's a lot of unique queries, increase the query cache size.

The easy approach is to run MySQLTuner after the MySQL or MariaDB server has been up for at least a week, and go through its suggestions.

There shouldn't be a significant difference in performance between PostgreSQL and MySQL/MariaDB if both have been optimized. Out-of-the-box config isn't ideal for a production system.

Heads up, you can also get postgress to use a socket and mount that through for another speedup if you haven't already

I've been a proponent here for a few months on using postgres/redis every time someone shits on NC for performance. While I agree the database change itself isn't a huge improvement, it pays for itself long term in larger volume installs when you and your organization/group get using it heavily. The redis connected on socket like the AIO mastercontainer sets up is where the real juice comes from, but only on an install that gets used so it caches properly. The first time you fire it up, it's pretty slow but as it gets used, things are much better.

I'm going to try this next week. My nextcloud instance is getting a bit sluggish lately.

Thanks for sharing it, really helpful post

ive tried to get nextcloud working several times and it just seems to never work for some reason... maybe i should set it up on a pi ive got laying around instead of my main server lol

I had been running Nextcloud on an old laptop using Ubuntu, but that machine died. I have a Windows PC originally built for gaming that I am considering using for Nextcloud. Anyone have any experience with NC and Windows? Thought on the DB switch on Windows?

Does Postgres really help that much? It runs fine for me with MariaDB

I wonder what performance impact there would be if you were to move pgsql onto bare metal with enough ram dedicated to caching all of the db data (think: i5 or i7 nuc). That's going to be my next step with my homelab; I want to migrate everything to a single db host with a lot of RAM and M2 storage and avoid the db process replication I have going on. I have no performance complaints with NC currently, I'm running PHP cache and redis as well as image preview and imaginary.

Is there a way to self-host nextcloud by downloading one file, docker container, .nzb, .jpg, ANYTHING that includes all these parts and can just plug in and run? Is that a thing, or do all self-hosters spend every waking hour sudo updating?

Since i started using nixos i don't have any problems with nextcloud 🙃