WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #40613


Ignore:
Timestamp:
04/30/2017 06:46:03 PM (3 years ago)
Author:
johnjamesjacoby
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #40613 – Description

    initial v1  
    33Note that each individual user object is cached, and that query caches will need to be invalidated when users are added/removed/edited.
    44
    5 Theoretically, on busy sites with many users who are constantly changing passwords and things, caching user queries may not yield a significant performance improvement. For the majority of installations (where users are not shifted around nearly as much) this could be result in several additional cache hits per page load (especially with persistent caches in place.)
     5Theoretically, on busy sites with many users who are constantly changing passwords and things, caching user queries may not yield a significant performance improvement. For the majority of installations (where users are not shifted around nearly as much) this could result in several additional cache hits per page load (especially with persistent caches in place.)
     6
     7Functions like `wp_dropdown_users()` are called multiple times when viewing the Posts list-table, and many plugins also call `get_users()` knowing that user objects are cached (but not noticing the additional database hits for each call itself.)
     8
     9Membership plugins like BuddyPress would have inherent benefits, and bbPress could operate more efficiently when querying for the intersection of many topics with many users who are engaged in them.
    610
    711Patch imminent.