You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Excessive database usage for information that changes rarely. On my personal instance with fairly little activity the name lookup in oc_authtoken is the second most executed query on the authtoken table. Details are found in nextcloud/server#42574.
if (preg_match('/ \(Talk Desktop Client - [A-Za-z ]+\)$/', $row['name'])) {
$result->closeCursor();
returntrue;
}
}
$result->closeCursor();
returnfalse;
}
}
We can cache this information, even if it's just for a few minutes.
Server configuration
Operating system:
Web server:
Database:
PHP version:
Nextcloud version: 26.0.9
Where did you install Nextcloud from:
Signing status:
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Nextcloud configuration:
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Client configuration
Browser:
Operating system:
Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
The text was updated successfully, but these errors were encountered:
Excessive database usage for information that changes rarely.
Well the problem is there is a "timing constraint" on the query. It checks for clients that contacted the server in the last 120 seconds, to avoid duplicate notifications. I'm not sure sure how long we could cache this information, given that the info is used every ~30 seconds when a client pulls notifications.
However we could skip the query when the Talk app is not enabled at all.
But other than that I'm not sure this makes a lot of sense if we don't make it 2 queries:
has a talk client - cachable for ~5-10 minutes?
if 1 is true run a second query to check the timing constraint
Steps to reproduce
Expected behaviour
Lean datatabase usage.
Actual behaviour
Excessive database usage for information that changes rarely. On my personal instance with fairly little activity the
name
lookup in oc_authtoken is the second most executed query on the authtoken table. Details are found in nextcloud/server#42574.notifications/lib/Service/ClientService.php
Lines 41 to 65 in 27a3784
We can cache this information, even if it's just for a few minutes.
Server configuration
Operating system:
Web server:
Database:
PHP version:
Nextcloud version: 26.0.9
Where did you install Nextcloud from:
Signing status:
List of activated apps:
Nextcloud configuration:
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Client configuration
Browser:
Operating system:
Logs
Nextcloud log (data/nextcloud.log)
Browser log
The text was updated successfully, but these errors were encountered: