New Proposal Calls for Automated Performance Monitoring for WordPress Core
WordPress Core Committer Adam Silverstein has published a proposal for adding automated performance tooling that would offer continuous monitoring for performance issues so they can be resolved before major regressions are committed to core. “Similar to our unit test suite, automated performance testing would help protect core from introducing large performance regressions by catching problems immediately and tracking performance over time,” Silverstein said. “Automating testing also means saving contributor effort by replacing a time consuming manual process.” As the Performance team is focused on introducing new features with measurable gains, as well as testing new WordPress releases before they ship, they have haphazardly uncovered what Silverstein described as “significant performance regressions.” A few examples include a regression found before WP 6.1 in theme.json processing and another issue with changes for loading the textdomain. “Automated testing would catch this type of regression as soon as it was introduced, making it much easier to resolve,” he said. Silverstein highlighted the Gutenberg project as a good example of performance tracking, as each release publishes metrics for changes in loading time, typing time, and block selection time. The team has also begun tracking TTFB (time to first byte) for classic versus block themes in their code health dashboard,…
…Full post on WP Tavern
Read Full
