Skip to content
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

Closed
fl4p opened this issue Oct 13, 2017 · 6 comments
Closed

Performance #612

fl4p opened this issue Oct 13, 2017 · 6 comments

Comments

@fl4p
Copy link

fl4p commented Oct 13, 2017

@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.

@fl4p fl4p changed the title get_plugins Performance Oct 13, 2017
@afragen
Copy link
Owner

afragen commented Oct 13, 2017

Have you tried the develop branch?

@afragen
Copy link
Owner

afragen commented Oct 14, 2017

Thanks for opening this ticket, https://core.trac.wordpress.org/ticket/42217

afragen added a commit that referenced this issue Oct 14, 2017
Current default is for 5 minutes
#612
@afragen
Copy link
Owner

afragen commented Oct 14, 2017

@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.

597ca95

@afragen
Copy link
Owner

afragen commented Oct 15, 2017

Timeout increased to 30 minutes. 845e9a6

@afragen
Copy link
Owner

afragen commented Oct 18, 2017

@f4bsch I’m curious to see what kind of improvements you see with the develop v7.3.1.23

@afragen afragen closed this as completed Oct 18, 2017
afragen added a commit that referenced this issue Apr 26, 2018
reverts #612
hopefully fixes #637 and #662
@afragen
Copy link
Owner

afragen commented Apr 26, 2018

I have to revert this as I think it's causing #662 and possibly #637

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants