[wp-trac] [WordPress Trac] #54221: _transient_dirsize_cache is set to autoload=yes and kills db performance if it grows (20MB in our case)

[WordPress Trac]

#54221: _transient_dirsize_cache is set to autoload=yes and kills db performance if
it grows (20MB in our case)
------------------------------+------------------------------------------
 Reporter:  archon810         |       Owner:  spacedmonkey
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  6.4
Component:  Database          |     Version:  2.8
 Severity:  major             |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:  administration, performance
------------------------------+------------------------------------------

Comment (by raxvegasaenz):

 Replying to [comment:57 chvillanuevap]:
 > I also encountered this issue with the dirsize_cache transient option
 growing in size (it was pointed out by my host, WP Engine). After seeing
 this fix and upgrading to WordPress 6.4, I noticed the issue persisted,
 with the variable still set to autoload='yes' in the database. I think
 it's important for future visitors of this thread to understand that the
 fix introduced in this update is not retroactive, as previously mentioned.
 If you need an immediate fix, you can:
 >
 > 1. Manually delete the transient from the database (it will be recreated
 later with the expiration date implemented in this patch).
 > 2. Alternatively, set autoload to 'no'.
 >
 > These steps were crucial for the 6.4 patch to work.

 @chvillanuevap, I have faced this issue too and **solved it today just by
 clearing domain cache in WPEngine**, as the main problem was that we were
 not able to see changes in frontend resources from time to time, not even
 after deleting object, network, page and local cache on server side and
 ours, respectively. But regarding the record at WP_OPTIONS table, it was
 bloated too in dev environment; clearing it helps but definitely I would
 not change the autoload option, however I deleted that record just in
 case, and at this moment it has not caused any issues so far.

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