diff options
| author | Roeland Jago Douma <roeland@famdouma.nl> | 2019-07-16 19:10:09 +0200 |
|---|---|---|
| committer | Backportbot <backportbot-noreply@rullzer.com> | 2019-07-17 05:48:53 +0000 |
| commit | 7bd081ff8417981a673f635acf154aa72947c2d7 (patch) | |
| tree | 478c409ad87b9074fd20382b4c347d5ea79a41cb /apps | |
| parent | f42afb059e6be95fcf3682ebe99935ada5150c14 (diff) | |
| download | nextcloud-server-7bd081ff8417981a673f635acf154aa72947c2d7.tar.gz nextcloud-server-7bd081ff8417981a673f635acf154aa72947c2d7.zip | |
Do not keep searching for recent
If userA has a lot of recent files. But only shares 1 file with userB
(that has no files at all). We could keep searching until we run out of
recent files for userA.
Now assume the inactive userB has 20 incomming shares like that from
different users. getRecent then basically keeps consuming huge amounts
of resources and with each iteration the load on the DB increases
(because of the offset).
This makes sure we do not get more than 3 times the limit we search for
or more than 5 queries.
This means we might miss some recent entries but we should fix that
separatly. This is just to make sure the load on the DB stays sane.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Diffstat (limited to 'apps')
0 files changed, 0 insertions, 0 deletions