-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Certain user admin pages slow to load #6980
Comments
I've noted this too. I wonder if it might be an idea to paginate the annotations and tracks on user accounts, so as to minimise the load time. As an example, I loaded user 802's profile in admin view - the profile took 20 seconds to appear. That's very slow. One potential downside of pagination would be that it could be a nuisance for Information Rights requests - but, given we already have this in place for lists of requests in user admin views, I doubt it's going to be a big issue. |
One could have a button linking to an non-paginated version for IR requests. Perhaps linked to #6267. |
While pagination is likely the solution here, there's more we could do on the caching front within the admin interface (#1006). |
Workaround: Click the "revert to admin button", and don't wait for my user admin page to load, load another page instead. |
This only helps with switching back to my admin account, it doesn't help with switching to the /user/whatdotheyknow account |
I've just timed it, there's a ~12 second delay currently opening the /user/whatdotheyknow admin page- it's not major, maybe we're just used to speedy page loads online now! My own user account's admin page took ~22 seconds to load, but as noted there's a workaround for that when switching between accounts. |
The admin page for my account and the /user/WhatDoTheyKnow account take 10-15 seconds to load.
Both my account and /user/WhatDoTheyKnow have lots of annotations on them.
I've noticed this particularly while using the new feature: "Button for admins to revert to their own account after logging in as a user" #1785
The text was updated successfully, but these errors were encountered: