[wp-trac] [WordPress Trac] #45471: Allow caching of parse_blocks results

WordPress Trac noreply at wordpress.org
Mon Jun 27 13:52:04 UTC 2022


#45471: Allow caching of parse_blocks results
-------------------------------------------------+-------------------------
 Reporter:  joostdevalk                          |       Owner:  francina
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.1
Component:  Cache API                            |     Version:  5.0
 Severity:  normal                               |  Resolution:
 Keywords:  needs-unit-tests needs-patch dev-    |     Focuses:
  feedback                                       |  performance
-------------------------------------------------+-------------------------

Comment (by dmsnell):

 @mukesh27 it's been a while since looking at this. I'm wondering if we
 know if we need it. Do we have evidence that parsing the blocks is causing
 performance issues? For most posts the parsing stage is still extremely
 fast. I worry that introducing it preemptively in Core could have negative
 side-effects and possibly slow down typical page views.

 The option to build one's own caching parser via a WordPress plugin
 remains and is a good option for handling special cases where for some
 reason the parsing is measurably slow.

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


More information about the wp-trac mailing list