[wp-trac] [WordPress Trac] #37923: Introduce shared wp_blogmeta database table for multisite installation

WordPress Trac noreply at wordpress.org
Thu Aug 24 15:04:03 UTC 2017


#37923: Introduce shared wp_blogmeta database table for multisite installation
-------------------------------------------------+-------------------------
 Reporter:  johnjamesjacoby                      |       Owner:
     Type:  feature request                      |  spacedmonkey
 Priority:  normal                               |      Status:  assigned
Component:  Networks and Sites                   |   Milestone:  4.9
 Severity:  normal                               |     Version:
 Keywords:  has-patch has-unit-tests needs-      |  Resolution:
  testing ms-roadmap                             |     Focuses:  multisite
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 I think there is a performance issue around loading from a different
 network's option. In standard bootstrap process, the current networks
 options are primed in memory. This is so even if you are not using object
 caching, some of the network options are loaded into memory. See
 wp_load_core_site_options. Calling a network option from a different
 network will result in another query / cache get. This is made worse by
 #37181 as the meta api, saves all of it's data in one cache key. The
 result would mean, calling an network option, it would load the lot into
 memory. There are network transient that can be bulky.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/37923#comment:63>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list