Skip to content

Performance regression in 31 with co-owner shares #52510

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.

Sign up for GitHub

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

Jump to bottom
Open
icewind1991 opened this issue Apr 28, 2025 · 0 comments
Open

Performance regression in 31 with co-owner shares #52510

icewind1991 opened this issue Apr 28, 2025 · 0 comments
Assignees
@provokateurin
Labels
1. to develop Accepted and waiting to be taken care of 31-feedback bug performance 🚀
Milestone
Nextcloud 32

Comments

@icewind1991
Copy link
Member

The co-owner shares introduced in #49073 causes a performance regression as mentioned in #49073 (review) due it it now having to query shares for each file in a folder.

Possible solution would be:

  • create a new extension interface to allow listing shares in a folder without the sharee filter
  • for any 3rd party share backend not implementing the new interface, just fall back to disabling co-owners
@icewind1991 icewind1991 added this to the Nextcloud 32 milestone Apr 28, 2025
@provokateurin provokateurin moved this to 📄 To do (~10 entries) in 📁 Files team Apr 28, 2025
@provokateurin provokateurin added bug 1. to develop Accepted and waiting to be taken care of performance 🚀 labels Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@provokateurin provokateurin

Labels
1. to develop Accepted and waiting to be taken care of 31-feedback bug performance 🚀
Projects
📁 Files team
Status: 📄 To do (~10 entries)
Milestone
Nextcloud 32
Development

No branches or pull requests
3 participants
@icewind1991 @provokateurin @szaimen