Make WordPress Core

Opened 8 years ago

Last modified 3 years ago

#27776 new defect (bug)

WordPress API timeouts should be cached to avoid slowing down the admin

Reported by: brandonwamboldt's profile brandon.wamboldt Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.3
Component: Administration Keywords:
Focuses: performance Cc:


The admin does several calls to the WordPress API, such as from the wp_check_browser_version function. These calls don't cache timeouts, which means if the API is consistently timing out the admin is slow on every load as all of these calls must timeout before the page can load.

I propose we cache timeouts using transients, for a day.

This behavior has been present since at least 3.3 and is still the behavior on trunk.

Change History (5)

#2 @MikeHansenMe
8 years ago

I too have run into this problem.

#3 @DrewAPicture
7 years ago

  • Component changed from General to Administration
  • Focuses administration removed

#4 @DrewAPicture
7 years ago

  • Focuses performance added

#5 @valendesigns
7 years ago

I think caching for an entire day could be overkill, since the problem could be intermittent and not last 24 hours. Something along the lines of 30 minutes seems reasonable enough to free up resources and still be actively looking for an API connection.

Note: See TracTickets for help on using tickets.