mirror of
https://github.com/nextcloud/server.git
synced 2026-02-15 16:59:47 -05:00
7dd7256cfe
The auth token activity logic works as follows * Read auth token * Compare last activity time stamp to current time * Update auth token activity if it's older than x seconds This works fine in isolation but with concurrency that means that occasionally the same token is read simultaneously by two processes and both of these processes will trigger an update of the same row. Affectively the second update doesn't add much value. It might set the time stamp to the exact same time stamp or one a few seconds later. But the last activity is no precise science, we don't need this accuracy. This patch changes the UPDATE query to include the expected value in a comparison with the current data. This results in an affected row when the data in the DB still has an old time stamp, but won't affect a row if the time stamp is (nearly) up to date. This is a micro optimization and will possibly not show any significant performance improvement. Yet in setups with a DB cluster it means that the write node has to send fewer changes to the read nodes due to the lower number of actual changes. Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at> |
||
|---|---|---|
| .. | ||
| acceptance | ||
| apps | ||
| Core | ||
| data | ||
| docker | ||
| lib | ||
| objectstore | ||
| Test/Repair/Owncloud | ||
| travis | ||
| apps.php | ||
| bootstrap.php | ||
| drone-run-integration-tests.sh | ||
| drone-run-php-tests.sh | ||
| drone-wait-objectstore.sh | ||
| enable_all.php | ||
| jestBabelTransformer.js | ||
| jestSetup.js | ||
| karma.config.js | ||
| phpunit-autotest-external.xml | ||
| phpunit-autotest.xml | ||
| preseed-config.php | ||
| redis-cluster.config.php | ||
| redis.config.php | ||
| startsessionlistener.php | ||