[wp-trac] [WordPress Trac] #60787: get_registered_meta_keys() should allow for late registration to improve performance

[WordPress Trac]

#60787: get_registered_meta_keys() should allow for late registration to improve
performance
--------------------------------+------------------------------
 Reporter:  sc0ttkclark         |       Owner:  (none)
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Options, Meta APIs  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  has-patch           |     Focuses:  performance
--------------------------------+------------------------------

Comment (by sc0ttkclark):

 @jorbin I don't have any tests to show the impact at scale for this yet.

 For storing configs in DB vs File, there's a segment of people who use
 these plugins that would be aware of that kind of thing. For example, ACF
 itself has 2+ million active installs, but people must pay for a separate
 ACF Pro plugin to get access to a local JSON feature.

 Many Custom Field plugins I've seen have not attempted to utilize
 `register_meta()` because of the impact on every page load but that
 adoption will increase with the Block Bindings API for Post Meta in WP
 6.5.

 ACF only recently included `register_meta()` usage but not for every
 custom field -- only for a unique ACF field that for handling custom field
 revisions (a WP 6.4 feature) outside of core logic.

 @jorbin I can look into how to test the performance differences between a
 theoretical ACF customization that attempted to do that logic in WP 6.5 vs
 the new way from my PR. Any suggestions on how to gather that info or
 would just comparing stats from Query Monitor be enough?

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