The Core team is requesting feedback from Web Hosts and DBAs on the following PRs and configurations for RTC architecture:
It's official, RTC will get it's own shiny new wp_collaboration database table.
PR #11256 establishes a foundational table schema for a single custom table.
PR #11348 uses the transients API for state awareness, with persistent cache awareness stored in object cache, and reduced awareness granularity to ~10 seconds which reduces database writes/cache invalidation.
PR #11599 outlines a hybrid approach that combines the concepts in the first two PRs. This adds the custom database table for storage, stores awareness in object cache when available so no attempt at writes are made, and falls back on storing awareness in the table if persistent cache is not enabled.
PR #11609 adds an additional wp_presence dedicated table for awareness storage. This is likely to be on the roadmap for 7.1 rather than 7.0, but feedback is wanted and appreciated!
All of these have their considerations, and need to be tested on a wide variety of hosting configurations, while feedback from web hosts and DBAS is needed on the architecture outlined in the PRs above.
How can hosts test?
For those of you who are already testing, thank you so much! Feedback on the PRs, and any testing data or analysis you have can be shared in the comments here on this ticket.
This RTC test suite was created by Core to collect data on the RTC feature in WordPress 7.0, to help assess and inform the path forward for the supporting RTC architecture, and guarantee the feature is as performant as it can be on hosting systems and user sites.
A new test report type has been integrated in to the php-test-runner, so if Hosts run the test suite within their runner config, it will report directly back to Core.
Some hosts have not sent test reports through the Hosting team runner in some time, and if that's you please check on your test runner!
If your org is not yet reporting test data, you can get started with distributed testing here.
As you know, the RTC feature will undergo major architectural changes in the coming weeks with consideration for hosting feedback. Two more RC versions of 7.0 are pending release, with 7.0 RC3 due for release on May 8th. While RC3 will be an RC in name, it needs to be tested as if it's a Beta 1, and feedback from hosts is needed prior to the next RC3 release.
Testing on the part of hosts is particularly important to establish RTC architecture that is optimally compatible and performant on all hosting systems. Participating in testing this feature will help make sure the release of 7.0 rolls out as smoothly as possible on hosting systems, for support teams and most importantly, for WordPress users. Thank you so much for your help testing, for reporting via distributing testing, and for sharing any feedback and test data in the comments below!
The Core team is requesting feedback from Web Hosts and DBAs on the following PRs and configurations for RTC architecture:
It's official, RTC will get it's own shiny new
wp_collaborationdatabase table.PR #11256 establishes a foundational table schema for a single custom table.
PR #11348 uses the transients API for state awareness, with persistent cache awareness stored in object cache, and reduced awareness granularity to ~10 seconds which reduces database writes/cache invalidation.
PR #11599 outlines a hybrid approach that combines the concepts in the first two PRs. This adds the custom database table for storage, stores awareness in object cache when available so no attempt at writes are made, and falls back on storing awareness in the table if persistent cache is not enabled.
PR #11609 adds an additional
wp_presencededicated table for awareness storage. This is likely to be on the roadmap for 7.1 rather than 7.0, but feedback is wanted and appreciated!All of these have their considerations, and need to be tested on a wide variety of hosting configurations, while feedback from web hosts and DBAS is needed on the architecture outlined in the PRs above.
How can hosts test?
For those of you who are already testing, thank you so much! Feedback on the PRs, and any testing data or analysis you have can be shared in the comments here on this ticket.
This RTC test suite was created by Core to collect data on the RTC feature in WordPress 7.0, to help assess and inform the path forward for the supporting RTC architecture, and guarantee the feature is as performant as it can be on hosting systems and user sites.
A new test report type has been integrated in to the php-test-runner, so if Hosts run the test suite within their runner config, it will report directly back to Core.
Some hosts have not sent test reports through the Hosting team runner in some time, and if that's you please check on your test runner!
If your org is not yet reporting test data, you can get started with distributed testing here.
As you know, the RTC feature will undergo major architectural changes in the coming weeks with consideration for hosting feedback. Two more RC versions of 7.0 are pending release, with 7.0 RC3 due for release on May 8th. While RC3 will be an RC in name, it needs to be tested as if it's a Beta 1, and feedback from hosts is needed prior to the next RC3 release.
Testing on the part of hosts is particularly important to establish RTC architecture that is optimally compatible and performant on all hosting systems. Participating in testing this feature will help make sure the release of 7.0 rolls out as smoothly as possible on hosting systems, for support teams and most importantly, for WordPress users. Thank you so much for your help testing, for reporting via distributing testing, and for sharing any feedback and test data in the comments below!