[wp-trac] [WordPress Trac] #36906: Comment caches should be persistent

WordPress Trac noreply at wordpress.org
Sun May 22 16:01:55 UTC 2016


#36906: Comment caches should be persistent
--------------------------+----------------------------
 Reporter:  boonebgorges  |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Future Release
Component:  Comments      |    Version:  2.2
 Severity:  normal        |   Keywords:
  Focuses:  performance   |
--------------------------+----------------------------
 The 'comment' cache group is non-persistent. We should try to make it
 persistent.

 To make the change, we'll need a full review of how the 'comment' group is
 used throughout core. It's likely that there are many places where we
 don't bother invalidating because the cache only lasts for the page load.

 It may be possible to phase in the persistent cache by breaking the
 'comments' group into two or more pieces. I'm thinking specifically of
 individually cached comments (eg `wp_cache_set( $comment_id,
 $comment_object, 'comment' )`) vs all other uses of the 'comment' group
 (ID queries, etc). It's likely going to be easier to cover all the
 invalidation cases for single comments.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/36906>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list