Following the removal of real-time collaboration (RTC) from WordPress 7.0, performance testing data from eight hosting environments was analyzed to determine the best storage strategy. Four candidates were tested: post-meta, custom-table, post-meta-transients, and custom-table-with-transients. The custom-table-with-transients approach was fastest or tied-first in six of seven environments, averaging ~52% faster than the RC2 baseline. It reduces database queries to one per dispatch when a persistent object cache is present, and benefits from the custom-table schema efficiency when caching is absent. The post-meta-transients strategy is explicitly not recommended due to severe latency degradation without a persistent cache. The recommendation is to use custom-table-with-transients as the default RTC storage strategy for future development.
Sort: