• We have had several sites with issues where the wp_options table crashes. This is usually due to too many entries in the table with autoload = ‘yes’ from plugins.

    I found that your plugin fetches the Google Font library and stores the entire wp_remote_url response as json into the wp_options table under “googlefonts_data” and is responsible for half of the size of all wp_options that autoload when a page is loaded on one of our sites. (over 570KiB)

    To fix this, I believe you need to set autoload to ‘no’ when you create/update the option. To provide a better experience, I would suggest saving the data somewhere other than wp_options or only requesting that data when the admin loads the settings page and not storing that api response in the database at all.

  • The topic ‘Extremely large wp_options cache’ is closed to new replies.