-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avatar performance improvements #22414
Comments
Isn't the avatar something like a thumbnail? Or should we store it in a dedicated location? Maybe related #25213 |
I'd suggest storing it outside of "/files" so we don't need a full FS setup just to access it. Maybe a proper location would be "data/$user/avatar", then if there are multiple sizes they can just be stored there. |
I'm setting this to 9.2 because this have more consequences on performance and other nasty side effects. |
agreed |
Hmmm, just now I thought about modifying |
PR to move avatars: #25790 |
Is the solution from 9.2 that moves the avatars to separate folders already enough to move this ticket to backlog and decrease severity @DeepDiver1975 @butonic ? |
Decreasing severity to high |
moving to backlog for now. Time will tell whether the 10.0 solution of having a separate avatar folder is enough to reduce the severity of this issue. Additional tasks are still valid to further improve avatar handling. |
Also linking #26872 here in case it contributes to decreasing severity and/or close. |
This issue has been automatically closed. |
Curerntly we just store the avatars in
/<user>/avatar.jpg
(or<user>/avatar.png
). While this is simple it also has certain drawbacks. Like the bug we hit with #22119Further more it would be great to also get avatars of trusted ownClouds locally since we have the vcards anyway.
So basically we should rethink our avatar handling in general.
CC: @PVince81 @DeepDiver1975
The text was updated successfully, but these errors were encountered: