I have some broad questions about web UI performance.
Does v30/hub 9 include any significant performance improvements?
In v29 and earlier, does it matter that static assets (JS, CSS) are not combined?
Are there any public/community performance target metrics, benchmark scripts, goals, or a roadmap for future changes?
I have a self-hosted Nextcloud instance using the Docker community image, currently v29.0.7. MariaDB backend, valkey (redis replacement) enabled. In general everything feels fast enough to be useful–no complaints here. When I time, say, fetching /apps/files/ logged in with a primed cache, it takes about 5 seconds before network activity idles. This seems big? I don’t know. Subsequent clicks descending into folders takes about 1sec per click, and traversing to parent folders is too fast to tell.
Any ideas/suggestions for simple things I could do to keep track of server performance besides these timings above? Something from the command line would be nice.
in earlier version, they had such an option, but I think with the different apps that was not working out great.
The first time you load the page, it takes quite some time and some of the static assets can be quite large. But your timings seem normal to me.
Good question, perhaps the developers use tools to monitor the performance. If it degrades quickly, then it could be an indicator for a bug, and on the long-term it could be interesting to improve the performance.
You can use the browser dev tools (F12) and there network analysis. There you can see all loaded objects. You can use Strg / Ctrl + F5 to reload all. Then you can see a difference between load from cache and new/first load.
In network analysis you can also sort the size of the objects. core-common.js e.g. needs 5 MB. But I think that Nextcloud has really been optimised over the last few releases.
You can open about:cache (in Firefox) and search e.g. core-common.js for correct caching and using.