Performance improvements to get_user_data_from_wp_global_styles

[spacedmonkey]

The get_user_data_from_wp_global_styles in the WP_Theme_JSON_Resolver class have a number of performance issues. These include by are not limited to.

The following params should be passing the WP_Query object to increase performance.

'ignore_sticky_posts'    => true,
'suppress_filters'       => false,
'update_post_meta_cache' => false,
'update_post_term_cache' => false,
'lazy_load_term_meta'    => false,
'no_found_rows'          => true,
'suppress_filters'       => false,

• Cache invalidation now happens when posts are not updated and not just on an hour.
• Handle if wp_insert_posts returns a WP_Error.
• Only return ids in query, to make query simplifier.

Trac ticket: https://core.trac.wordpress.org/ticket/55392

[spacedmonkey]

Before

[spacedmonkey]

After

I have added some improved unit tests and tweaked this function so it now caches even more.

CC @oandregal @Mamaduka for a review, as they have worked on this function in the past.

I think this is great, but I wonder if this wouldn't be better as a Gutenberg PR instead of a core patch. i fear that if a gutenberg specific resolver class is added in compat merging will be hell.

@draganescu Now that this code lives in core, should PR not be done here? Would this not mean that have to port it over, adding more steps. This process, is not documented and is confusing me to.

This process, is not documented and is confusing me to.

This is true! But the code is still being heavily changed so I think to make Gutenberg plugin merges simpler we should not patch core with anything that is related to Gutenberg and can be created as a Gutenberg patch /PR.

[adamsilverstein]

@spacedmonkey this looks like a solid performance enhancement, bravo! Love to see these wins in theme code as well since it is so potentially impactful.

I see some failing tests under PHP 7.4 on the PR - is there anything else needed before this can land?

[spacedmonkey]

I have spent a little time on this. This change is still worth merging, as it skipping all the logic in WP_Query takes away some over head.

I will look into why tests are failing and merge.

[spacedmonkey]

@adamsilverstein Can you review again. Tests are now passing.

[mukesh27]

@spacedmonkey look solid, I left some feedback on the PR.

[spacedmonkey]

In 54186:

Posts, Post Types: Improve performance of the get_user_data_from_wp_global_styles method.

Improve the logic found in get_user_data_from_wp_global_styles method. Replace call to wp_get_recent_posts with the more standard, WP_Query for consistancy. Use transient over standard cache, to improve performance on sites without persistent object caching. Improve handling of cases where wp_insert_post returns a WP_Error.

Props spacedmonkey, adamsilverstein, mukesh27, peterwilsoncc, andregal.
Fixes #55392.

Committed into core.

[kebbet]

Latest changeset goes against #54518, see [52280]

Trac ticket: https://core.trac.wordpress.org/ticket/55392

Thanks for flagging the issue.

In core we use similar core reference tickets. There is no specific format for this type of document.

​https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/rest-api/endpoints/class-wp-rest-menu-items-controller.php#L331
​https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/rest-api/endpoints/class-wp-rest-menu-items-controller.php#L333
​https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/blocks/gallery.php#L84

Let's update the message and use period at end.

// Do not make string translatable, see https://core.trac.wordpress.org/ticket/54518.

Thanks for flagging the issue.

In core we use similar core reference tickets. There is no specific format for this type of document.

​https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/rest-api/endpoints/class-wp-rest-menu-items-controller.php#L331 ​https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/rest-api/endpoints/class-wp-rest-menu-items-controller.php#L333 ​https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/blocks/gallery.php#L84

Let's update the message and use period at end.

// Do not make string translatable, see https://core.trac.wordpress.org/ticket/54518.

Thanks for your review @mukeshpanchal27. The two commits adds a preiod and removes ticket from the comment.

[mukesh27]

The PR looks good to me and ready for the commit.

@spacedmonkey Can you please review it?

[kebbet]

@spacedmonkey I can not see the reason why the post_title was made translatable in [54186]. Could you please review the PR that reverts that particular change?

[spacedmonkey]

In 54246:

Posts, Post Types: Post title should not be translatable in get_user_data_from_wp_global_styles method.

In [52280] wp_template_part and wp_template posts, made the title of the post created not translatable. This was changed [54186] by mistake. This commit reverts that change.

Follow up to [54186], [52280].

Props mukesh27, kebbet.
See #55392.

[spacedmonkey]

@kebbet @mukesh27

Thanks for the flag. Fixed in [54246].

Merged in https://core.trac.wordpress.org/changeset/54246