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

WordPress Trac noreply at wordpress.org
Thu Oct 27 15:57:05 UTC 2016


#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  |     Focuses:  performance
-------------------------------------+-----------------------------

Comment (by danielbachhuber):

 Thanks @rmccue, those examples were quite helpful.

 For the next person to run into this, here's [https://github.com/lcache
 /wp-lcache/pull/97 WP LCache's implementation (with tests)]. I didn't find
 splitting `alloptions` to be horrible, but having to keep record of the
 `alloptions` keys in a separate cache does seem a bit dodgy.

 So it's mentioned, WP LCache doesn't absolutely need to have a multi get
 implementation because most cache gets will be hitting its L1 cache
 (APCu). Other drop-ins will need to implement multi get as well to
 mitigate the performance impact of introducing hundreds of new cache keys.

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


More information about the wp-trac mailing list