[wp-trac] [WordPress Trac] #62057: Addressing Autosave Memory Issues

[WordPress Trac]

#62057: Addressing Autosave Memory Issues
-------------------------------------------+-----------------------------
 Reporter:  whyisjake                      |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  assigned
 Priority:  normal                         |   Milestone:  Future Release
Component:  Editor                         |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch dev-reviewed commit  |     Focuses:
-------------------------------------------+-----------------------------
Changes (by adamsilverstein):

 * owner:  adamsilverstein => (none)
 * milestone:  6.8 => Future Release


Comment:

 Reviewing this again, I'm not confident in making this change without
 additional evidence for its benefits. Rather than avoid the preload,
 avoiding loading the full content is probably a better route.

 Reviewing just the proposed change here (removing the preload):

 * The data is still loaded in full via the rest endpoint, the load is just
 shifted to a later point. Memory savings would be minimal overall - if
 that isn't the case, maye a test could show that?
 * The data still needs to be loaded over the network, so I don't think
 there are savings there.
 * It is not clear if the original reason for adding the preload is still
 relevant - eg. there is a risk of a regression here.

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