[wp-trac] [WordPress Trac] #63717: `fetch_feed()` fails to use data stored in transients.
WordPress Trac
noreply at wordpress.org
Sat Nov 15 01:32:41 UTC 2025
#63717: `fetch_feed()` fails to use data stored in transients.
--------------------------------------+----------------------------
Reporter: peterwilsoncc | Owner: peterwilsoncc
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 6.9
Component: External Libraries | Version:
Severity: normal | Resolution: fixed
Keywords: has-patch has-unit-tests | Focuses: performance
--------------------------------------+----------------------------
Comment (by westonruter):
I was confused why benchmarking server timing for the homepage with the
theme unit test data imported showed a ''huge'' improvement in 6.9 over
6.8. It turn out to be due to the Feed widget! When I benchmarked the
first page of posts, I saw the huge improvement, but when I benchmarked
the second page of posts, the large change went away. It was due to the
"Blocks: Widgets" post being on the first page, and this post includes the
Feed widget. When I benchmark server timing for just that one post with a
Feed widget, the isolated improvement is dramatic:
{{{
npm run research -- benchmark-server-timing --url=http://wp68.local
/blocks-widgets/ --url=http://wp69.local/blocks-widgets/ --number=100
--diff --output=md
}}}
||= URL =||= WP 6.8 =||= WP 6.9 =||= Diff (ms) =||= Diff (%) =||
|| Response Time (median) || 266.57|| 34.74|| -231.83|| -87.0%||
|| wp-before-template (median) || 11.95|| 7.86|| -4.09|| -34.2%||
|| wp-template (median) || 252.55|| 25.56|| -226.99|| -89.9%||
|| wp-filter-the_content (median) || 224.5|| 9.35|| -215.15|| -95.8%||
|| wp-total (median) || 264.56|| 33.4|| -231.16|| -87.4%||
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63717#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list