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

WordPress Trac noreply at wordpress.org
Tue Sep 17 17:50:03 UTC 2024


#62057: Addressing Autosave Memory Issues
--------------------------+-----------------------------
 Reporter:  whyisjake     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Autosave      |    Version:
 Severity:  normal        |   Keywords:
  Focuses:  rest-api      |
--------------------------+-----------------------------
 This is based on research put together by @tallulahhh. I am assembling
 this ticket as part of the WordCamp US Contributor day.

 > To put it in brief: Autosave handling loads too much unused stuff into
 PHP memory on editor load. This introduces risk of autosave-induced OOM at
 scale, and wastes memory and resources across the board. Thankfully, I’ve
 also found that it’s very simple to effectively address, and I don’t think
 it’s hyperbole to claim this has scope to save a significant amount of
 waste WP memory, transport and query complexity – platform-wide, and even
 globally.

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


More information about the wp-trac mailing list