Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #24044, comment 49


Ignore:
Timestamp:
10/26/2015 12:37:03 AM (9 years ago)
Author:
galbaras
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #24044, comment 49

    initial v1  
    1 I have a wp_options table with over 600,000 records, mostly WooCommerce sessions and transients, which used to load the initial "autoload" query in 2.5 seconds, just like yours. After creating a secondary index on "autoload", it's loading in 0.01 seconds and the site is MUCH faster in general, possibly because this query prevented table updates while it was being scanned without the index.
     1I have a wp_options table with over 600,000 records, mostly WooCommerce sessions and transients, which used to load the initial "autoload" query in 2.5 seconds, just like @francogilio. After creating a secondary index on "autoload", it's loading in 0.01 seconds and the site is MUCH faster in general, possibly because this query prevented table updates while it was being scanned without the index.
    22
    33To me, such a small index is not something that should be so strictly opposed, considering it affects a core query executed by every page. It's just likely to speed many sites up, including some sites whose owners don't know phpMyAdmin from a bar of soap.