Merlin.2160p.BDRip.x265.10bit@paradoxguitarist It's currently running on a Xeon Silver 4208 box with 32GB of RAM and SSD storage, so it shouldn't have any reason to be slow. Comparing it to the ones hosted for example by my university show that it probably is due to Nextcloud being PHP after all...
Malte Kerl@ruhrscholz Can you define slow? I run a Nextcloud with a few TB of data on a Ryzen 2400G and 32GB of RAM and it is usually limited by the IO speed of my storage.
@maker the actual transfer speeds are as good as it gets, the problem are mostly the initial page loads and all the frontend stuff in general
Fennix 
@ruhrscholz @maker interesting. Are you sure it isn't something else on the network? I'm running it in a VM image on an old Ryzen 1700X (Image has 2c/16GB devoted to it) and it's fast for me -- sub 1s to load up home screen from cache, ~2.5s uncached. The only noticeable slowness is if I try to browse pictures in a giant grid where it's trying to thumbnail on the fly.
I wonder what the profiler says but my shot in the dark says it's DNS.
@ruhrscholz @maker that would be odd on its own. Modern PHP is very fast in comparison to old PHP.
How are you deployed?
@fennix linux namespace container with Debian 12, Remi PHP 8.1, storage on SSD-cached ZFS array and PG database in another VM. Traffic completely local in all directions.
@ruhrscholz When you profile it, where does it spend its time? Both in-browser and on the backend I'd wonder about but I'd probably start with simple browser profiling just because it's easier than running Xdebug and looking at things.
It's strange because I've used basically that same setup (via docker) in the past. Currently I'm running a full VM using the Nextcloud AIO Image, and completely uncached it's taking me 1.68s to load, 2.48s to render the dashboard, which is very default (Weather, status, recent pics, calendar). This is on LAN.
@ruhrscholz @fennix Can you maybe describe a benchmarking scenario?
I usually don't use the webfrontend that much but when I do it appears to be reasonable fast.
I just logged in, opened a random directory and opened a docx file with only office within it and it took 4.2s, 1.8s and 2.1s (all measured only once).
If your setup yields similar times we just have different definitions of slow, otherwise you could probably still optimize sth (no clue what though).