[wp-trac] [WordPress Trac] #25344: Introduce *_network_meta() functions
WordPress Trac
noreply at wordpress.org
Mon Apr 10 22:54:41 UTC 2017
#25344: Introduce *_network_meta() functions
-------------------------------------------------+-------------------------
Reporter: jeremyfelt | Owner:
Type: enhancement | Status: reopened
Priority: normal | Milestone: Future
Component: Networks and Sites | Release
Severity: normal | Version: 3.0
Keywords: reporter-feedback has-patch needs- | Resolution:
testing | Focuses: multisite
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):
* keywords: reporter-feedback has-patch needs-testing needs-unit-tests =>
reporter-feedback has-patch needs-testing
Comment:
I did a little work on profiling this patch. The biggest change to
performance is the function wp_load_core_site_options.
Instead of loading on a 9 of core options, it now loads all of network
options on page load. On average the standard wordpress install has 31
rows in the network meta table. However, loading all the network options,
doesn't mean now queries, it just means one query that gets more rows.
Loading all network meta might be a problem if there are plugins that add
lots of network options.
If object caching is enabled, there is a possible effect on performance.
Before only the core keys were loaded on page load. Now, that all the keys
are loaded, it means that the admin terminal is faster and there are less
SQL queries.
There is no right answer here, I am just saying this change is going to
have an effect, for some positive and for some negative.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/25344#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list