Installation Performance after update

Nextcloud version:

Nextcloud Hub 3 (25.0.4)

Operating system and version:

Operating System: Linux 5.10.103-v7l+ armv7l
CPU: ARMv7 Processor rev 3 (v7l) (4 cores)
Memory: 3.75 GB

DB:

Type: mysql
Version: 10.5.15
Size: 49.4 MB

PHP version:

Version: 8.1.16
Memory limit: 512 MB
Max execution time: 3600
Upload max size: 1 GB
Extensions: Core, date, libxml, pcre, zlib, filter, hash, json, readline, Reflection, SPL, session, cgi-fcgi, bcmath, bz2, ctype, curl, dom, fileinfo, ftp, gd, gmp, iconv, standard, intl, ldap, mbstring, openssl, pcntl, PDO, pgsql, posix, imap, SimpleXML, sodium, sqlite3, xml, xmlwriter, zip, exif, mysqlnd, pdo_pgsql, pdo_sqlite, Phar, xmlreader, pdo_mysql, apcu, igbinary, redis, memcached, imagick, mcrypt, smbclient, libsmbclient, Zend OPcache

Since I upgrade to Nextcloud 25 from 24 I notice that using the UI is slower. Looking into the developers tools it looks like that requets have a big time “Waiting for for server response” (around 1sec). I’m running nextcloud docker on a OMV6 with raspbian installed on a RPi4 4gb. It was ok before the update.

Where can I look into to identify why it is happening?

Thank you

Most of the requests looks like this:

In the logs I have this error like one time per day:

Error	PHP	Error: dns_get_record(): A temporary server error occurred. at /config/www/nextcloud/lib/private/Http/Client/DnsPinMiddleware.php#83

Nextcloud server that takes too much time to answer. How can I identify what could cause it?

The last 4 numbers of the nginx log are: request_time upstream_response_time upstream_connect_time upstream_header_time

$request_time – Full request time, starting when NGINX reads the first byte from the client and ending when NGINX sends the last byte of the response body
$upstream_response_time – Time between establishing a connection to an upstream server and receiving the last byte of the response body
$upstream_connect_time – Time spent establishing a connection with an upstream server
$upstream_header_time – Time between establishing a connection to an upstream server and receiving the first byte of the response header
192.168.1.248 - - [25/Mar/2023:19:02:31 +0000] "GET /apps/dashboard/ HTTP/2.0" 200 9646 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.881 0.880 0.020 0.870
192.168.1.248 - - [25/Mar/2023:19:02:32 +0000] "GET /apps/activity/js/activity-sidebar.js?v=71c8fb49-0 HTTP/2.0" 200 373126 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.270 0.270 0.030 0.050
192.168.1.248 - - [25/Mar/2023:19:02:32 +0000] "GET /apps/activity/js/activity-dashboard.js?v=71c8fb49-0 HTTP/2.0" 200 341839 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.283 0.280 0.030 0.070
192.168.1.248 - - [25/Mar/2023:19:02:32 +0000] "GET /apps/viewer/js/viewer-main.js?v=71c8fb49-0 HTTP/2.0" 200 670644 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.712 0.710 0.260 0.280
192.168.1.248 - - [25/Mar/2023:19:02:32 +0000] "GET /ocs/v2.php/search/providers?from=%2Fapps%2Fdashboard%2F HTTP/2.0" 200 221 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.353 0.350 0.030 0.350
192.168.1.248 - - [25/Mar/2023:19:02:33 +0000] "GET /ocs/v2.php/apps/notifications/api/v2/notifications HTTP/2.0" 200 480 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.296 0.300 0.030 0.300
192.168.1.248 - - [25/Mar/2023:19:02:34 +0000] "PUT /ocs/v2.php/apps/user_status/api/v1/heartbeat?format=json HTTP/2.0" 200 119 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.400 0.390 0.030 0.390
192.168.1.248 - - [25/Mar/2023:19:02:34 +0000] "GET /ocs/v2.php/apps/activity/api/v2/activity/by HTTP/2.0" 200 872 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.557 0.550 0.030 0.550
192.168.1.248 - - [25/Mar/2023:19:02:34 +0000] "GET /apps/recommendations/api/recommendations/always HTTP/2.0" 200 314 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.929 0.930 0.030 0.930
192.168.1.248 - - [25/Mar/2023:19:02:34 +0000] "GET /ocs/v2.php/apps/user_status/api/v1/statuses/josex HTTP/2.0" 200 127 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.607 0.610 0.050 0.610
192.168.1.248 - - [25/Mar/2023:19:02:34 +0000] "PUT /ocs/v2.php/apps/user_status/api/v1/heartbeat?format=json HTTP/2.0" 200 119 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"0.618 0.620 0.050 0.620

How can I go further to understand what could cause this? Since hardware is the same and OS didn’t get any major update it looks like something is not working properly. Now it take dozens of seconds to open a photo.