WordPress.org

Make WordPress Core

Changes between Initial Version and Version 2 of Ticket #32474


Ignore:
Timestamp:
05/24/2015 01:03:23 AM (4 years ago)
Author:
westonruter
Comment:

Replying to nacin:

I think we're likely going to see alloptions go away in #31245, something I'm willing to try in 4.3. I'd be curious to see arguments here that don't involve alloptions.

As mentioned in the description, non-alloptions arguments for not using options for storing widget instances include:

  • Loading all instance settings data for all widgets even when they are not ever used is wasteful and inefficient. Imagine if all posts in the database had to be loaded into memory each time WordPress renders a template.
  • Updating a single widget instance is expensive when settings are stored in options because for each instance change, the entire dataset for the widget type has to be unserialized. (Especially in the Customizer, #32103.)
  • For Memcached Object Cache specifically, when the number of widgets of a given type grows large enough it will breach the 1MB limit and no longer be cacheable.

Using a custom post type for storing widget instances seems like an elegant WordPress-way to store this data and it brings with it several benefits, as noted in the ticket's description.

I'm working on finishing a proof of concept plugin that makes use of widget instances being passed around as ArrayIterators instead of intrinsic arrays.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #32474 – Description

    initial v2  
    1 Widget instance data has always been stored in `wp_options`. This worked fine when there were only a few widgets used on a site. When there are hundreds—or thousands—there are big performance problems. When initializing widgets, Core loads the entire settings arrays of all widgets even when they are not used (#23909). Additionally, widget settings options are by default autoloaded: this means that for widget-heavy sites using Memcached Object Cache will reach the 1MB limit and crash since the autoloaded options will no longer be cacheable (WordPress.com even [https://github.com/Automattic/vip-quickstart/blob/master/www/wp-content/mu-plugins/alloptions-limit.php block a site from loading] in this scenario). Storage in autoloaded options also means widgets are susceptible to alloptions cache corruption (#31245). Bottom line: widgets stored in options are not scalable.
     1Widget instance data has always been stored in `wp_options`. This worked fine when there were only a few widgets used on a site. When there are hundreds—or thousands—there are big performance problems. When initializing widgets, Core loads the entire settings arrays of all widgets even when they are not used (#23909). In the Customizer, changes to widget settings is very expensive due having to unserialize and serialize option arrays repeatedly (#32103). Additionally, widget settings options are by default autoloaded: this means that for widget-heavy sites using Memcached Object Cache will reach the 1MB limit and crash since the autoloaded options will no longer be cacheable (WordPress.com even [https://github.com/Automattic/vip-quickstart/blob/master/www/wp-content/mu-plugins/alloptions-limit.php block a site from loading] in this scenario). Storage in autoloaded options also means widgets are susceptible to alloptions cache corruption (#31245). Bottom line: widgets stored in options are not scalable.
    22
    33As I've [https://core.trac.wordpress.org/ticket/31436#comment:2 mentioned elsewhere], widgets should ideally be stored in posts instead of options. In addition to improving the performance problems above, there are many advantaged to storing widgets as posts, including user attribution via `post_author`, revision history, import/export, querying, widget drafts, scheduled widgets,  etc.