[wp-trac] [WordPress Trac] #62790: "autoload" index is not used

[WordPress Trac]

#62790: "autoload" index is not used
-------------------------------+--------------------------
 Reporter:  kkmuffme           |       Owner:  joemcgill
     Type:  defect (bug)       |      Status:  reviewing
 Priority:  normal             |   Milestone:  6.9
Component:  Database           |     Version:  5.3
 Severity:  minor              |  Resolution:
 Keywords:  needs-patch early  |     Focuses:  performance
-------------------------------+--------------------------
Changes (by joemcgill):

 * keywords:  needs-patch => needs-patch early
 * milestone:  6.8 => 6.9


Comment:

 Replying to [comment:8 kkmuffme]:

 > Ironically, that feature achieved the opposite of what it set out to do
 though. By adding multiple different autoload values, it actually makes
 loading the options slower since the index isn't used anymore and if it is
 used (as seen by the "forced" cases) the query is actually slower in all
 cases except if you actually do have a huge option value which is
 prevented from being loaded.


 In some cases maybe so, but the feature ultimately set out to avoid auto-
 loading overly large options which has was measured to be a much larger
 performance problem then the time saved by ensuring the index is being
 used.

 Regardless, this conversation is getting off-topic from the point of this
 ticket, which is whether or not we should remove the index. I think it's
 worth gathering more data about the performance effects of doing so before
 making that change. I'm going to move this to the 6.9 milestone `early` so
 we have ample time to review and make a decision.

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