[wp-trac] [WordPress Trac] #64696: Real time collboration effectively disables persistent post caches while anyone edits a post

[WordPress Trac]

#64696: Real time collboration effectively disables persistent post caches while
anyone edits a post
--------------------------------------+--------------------------
 Reporter:  peterwilsoncc             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.0
Component:  Posts, Post Types         |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by westonruter):

 Replying to [comment:59 JoeFusco]:
 > **Require persistent  object cache:** Excludes a significant portion of
 the install base

 Note that in #56040 for WP 6.1, a Persistent Object Cache test was added
 to Site Health. It appears in the `production` environment. It has certain
 thresholds for whether the test fails:

 ||= Threshold =||= Value =||
 || `alloptions_count` || 500 ||
 || `alloptions_bytes` || 100,000 ||
 || `comments_count` || 1,000 ||
 || `options_count` || 1,000 ||
 || `posts_count` || 1,000 ||
 || `terms_count` || 1,000 ||
 || `users_count` || 1,000 ||

 If a persistent object cache becomes a requirement for RTC, the thresholds
 could be eliminated in favor of it always being recommended if RTC is
 enabled and the polling transport is being used.

 Nevertheless, shared hosting environments likely wouldn't provide
 Redis/Memcached to be able to enable a persistent object cache, so site
 owners would be stuck unless they upgrade. And for hosts that do provide
 Redis/Memcached, they may make available a WebSocket transport anyway.

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