[wp-trac] [WordPress Trac] #31245: Replace alloptions with a key cache

[WordPress Trac]

#31245: Replace alloptions with a key cache
-------------------------------------------+-----------------------------
 Reporter:  rmccue                         |       Owner:  rmccue
     Type:  enhancement                    |      Status:  assigned
 Priority:  normal                         |   Milestone:  Future Release
Component:  Options, Meta APIs             |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch needs-testing early  |     Focuses:  performance
-------------------------------------------+-----------------------------
Changes (by dd32):

 * keywords:  has-patch needs-testing 4.4-early => has-patch needs-testing
     early


Comment:

 Moving forward here, I think it's going to be fairly tough getting a
 viable `multi_get()` cache implementation in place for the majority of
 cache-enabled sites without significant detriment to the rest of the
 sites, as @tellyworth points out.

 > what do you think of solving this by clearing the alloptions cache at
 the right times
 @jeremyclarke Simply deleting the cache bucket isn't entirely viable for
 some users, as the next page load has the potential to cause a large DB
 load as many simultaneous requests hit a cold cache. However, that could
 easily be worked with with the next suggestion:

 > The approach of allowing the cache drop-in to support it's own
 alloptions gettings / setting would be better. Right now, this takes a
 crazy amount of hacking to do.

 This seems like a viable option to me, and I'm curious what it'd actually
 look like @joehoyle - @tollmanz @rmccue what do you think?

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