[wp-trac] [WordPress Trac] #38828: update_blog_details() performance improvement ideas

[WordPress Trac]

#38828: update_blog_details() performance improvement ideas
-------------------------------------------------+-------------------------
 Reporter:  boonebgorges                         |       Owner:
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
Component:  General                              |  Release
 Severity:  normal                               |     Version:
 Keywords:  needs-patch needs-unit-tests good-   |  Resolution:
  first-bug                                      |     Focuses:  multisite,
                                                 |  performance
-------------------------------------------------+-------------------------

Comment (by johnjamesjacoby):

 Most of WordPress is architected to trigger actions and bust caches when
 events on individual objects occur, and by-and-large this is the best way
 to stay thorough and maintain some sanity within the system.

 For actions like bulk-actions, updating counts, and updating last-activity
 (freshness), these are conceptually different in that it's likely to be
 much more efficient to only take action at the end, with certain per-
 object actions being superfluous (potentially extremely, I suspect.) Too
 bad `WP_Hook`'s can't intelligently unhook themselves under certain
 conditions.

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