perf: use more optimized way to get user storage info in ocs user info #49476
+61
−28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
icewind1991
requested review from
come-nc,
a team,
artonge and
yemkareems
and removed request for
a team
icewind1991
force-pushed
the
ocs-user-info-quota-optimize
branch
from
62119fc
to
1706c3e
Compare
Signed-off-by: Robin Appelman <[email protected]>
icewind1991
force-pushed
the
ocs-user-info-quota-optimize
branch
from
1706c3e
to
e004ce7
Compare
yemkareems
approved these changes
Nov 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of doing a full setup etc. We just get quota directly from the user, and the used space directly from the cache.
This means that we only need to setup the home storage for any user, instead of all storages the user has access to.
This does lead to a minor change in behavior, that for users with unlimited quota, the reported quota no longer falls back to the free space in the data directory. As far as I can tell these fields aren't used in the accounts ui and that behavior isn't something that can be relied on anyway, since s3 based setups (and various others) won't have this behavior anyway.