-
-
Notifications
You must be signed in to change notification settings - Fork 462
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
Performance #612
Comments
Have you tried the |
Thanks for opening this ticket, https://core.trac.wordpress.org/ticket/42217 |
Current default is for 5 minutes #612
@f4bsch I've been looking into this and I've got it working such that on my local dev with caching the lookup is 1-2 ms vs 300ms without caching. My question to you is, how long is long enough to cache? Currently I have it set to 5 minutes. |
Timeout increased to 30 minutes. 845e9a6 |
@f4bsch I’m curious to see what kind of improvements you see with the develop v7.3.1.23 |
@afragen closed #608, let me reformulate it:
github-updater triggers the WP API function
get_plugins()
on a lot of admin screens. This function scans the complete plugin directory, which can take a long time (I measured 600ms with 50 plugins in that directory).github-updater should cache the
get_plugins()
result and defer an update to a cron.I know that 50 plugins are a lot, but consider that that github-updater is an updater, and it should do it's job well. This means that it should be able to handle a lot of plugins, without clogging the admin screens.
The text was updated successfully, but these errors were encountered: