[wp-trac] [WordPress Trac] #62692: Performance regression for get_option in 6.4

WordPress Trac noreply at wordpress.org
Wed Dec 18 00:00:33 UTC 2024


#62692: Performance regression for get_option in 6.4
--------------------------------------+------------------------------
 Reporter:  rmccue                    |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Cache API                 |     Version:  6.4
 Severity:  major                     |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------

Comment (by siliconforks):

 Instead of reverting the change entirely, it is it possible to fix it so
 that it no longer has the issue?

 Looking at the code, it looks like the old behavior before [56595] was (in
 very high-level pseudocode):

 1. Check `notoptions`
 2. Check `alloptions`
 3. Check the cache for the specific option
 4. Check the database for the specific option

 The current behavior (since [56595] was committed) is:

 1. Check `alloptions`
 2. Check the cache for the specific option
 3. Check `notoptions`
 4. Check the database for the specific option

 It seems like what you really want is this:

 1. Check `alloptions`
 2. Check `notoptions`
 3. Check the cache for the specific option
 4. Check the database for the specific option

 Does that make sense?

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


More information about the wp-trac mailing list