[wp-trac] [WordPress Trac] #59532: Avoid registering block-patterns on the frontend

[WordPress Trac]

#59532: Avoid registering block-patterns on the frontend
--------------------------+--------------------------
 Reporter:  aristath      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.5
Component:  Editor        |     Version:  6.4
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  performance
--------------------------+--------------------------

Comment (by joemcgill):

 Given that patterns can be referenced in templates and will need to be
 registered in order to render properly, we either need to find a way of
 registering these on demand (i.e., lazy loading) rather than loading them
 all on every request, or find a way of making this registration process
 more performant.

 For the latter, improving the caching strategy for block patterns (related
 #60120) should help, but finding additional ways of making this process
 more performant without persistently caching patter data would be good to
 explore.

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