OllieJones

rjasdfiii

<h4>How do I use this plugin?</h4>
<p>After you install and activate this plugin, visit the Index MySQL Tool under the Tools menu. From there you can press the <em>Add Keys Now</em> button. If you have large tables, use it with <a href="https://wp-cli.org/" rel="nofollow ugc">WP-CLI</a> instead to avoid timeouts. See the WP-CLI section to learn more.</p>
<h4>What does it do for my site?</h4>
<p>This plugin works to make your MySQL database work more efficiently by adding high-performance keys to the tables you choose. On request it monitors your site’s use of your MySQL database to detect which database operations are slowest. It is most useful for large sites: sites with many users, posts, pages, and / or products.</p>
<p>You can use it to restore WordPress’s default keys if need be.</p>
<h4>What is this all about?</h4>
<p>Where does WordPress store all that stuff that makes your site great? Where are your pages, posts, products, media, users, custom fields, metadata, and all your valuable content? All that data is in the <a href="https://www.mysql.com/" rel="nofollow ugc">MySQL</a> relational database management system. (Many hosting providers and servers use the <a href="https://mariadb.org/" rel="nofollow ugc">MariaDB</a> fork of the MySQL software; it works exactly the same way as MySQL itself.)</p>
<p>As your site grows, your MySQL tables grow. Giant tables can make your page loads slow down, frustrate your users, and even hurt your search-engine rankings. And, bulk imports can take absurd amounts of time. What can you do about this?</p>
<p>You can install and use a database cleaner plugin to get rid of old unwanted data and reorganize your tables. That makes them smaller, and therefore faster. That is a good and necessary task. That is not the task of this plugin. You can, if your hosting provider supports it, install and use a <a href="https://developer.wordpress.org/reference/classes/wp_object_cache/#persistent-cache-plugins" rel="nofollow ugc">Persistent Object Cache plugin</a> to reduce traffic to your database. That is not the task of this plugin either.</p>
<p>This plugin adds database <a href="https://dev.mysql.com/doc/refman/8.0/en/mysql-indexes.html" rel="nofollow ugc">keys</a> (also called indexes) to your MySQL tables to make it easier for WordPress to find the information it needs. All relational database management systems store your information in long-lived <em>tables</em>. For example, WordPress stores your posts and other content in a table called <em>wp_posts</em>, and custom post fields in another table called <em>wp_postmeta</em>.  A successful site can have thousands of posts and hundreds of thousands of custom post fields. MySQL has two jobs:</p>
<ol>
<li>Keep all that data organized.</li>
<li>Find the data it needs quickly.</li>
</ol>
<p>To do its second job, MySQL uses database keys. Each table has one or more keys. For example, <code>wp_posts</code> has a key to let it quickly find posts when you know the author. Without its <em>post_author</em> key MySQL would have to scan every one of your posts looking for matches to the author you want. Our users know what that looks like: slow. With the key, MySQL can jump right to the matching posts.</p>
<p>In a new WordPress site with a couple of users and a dozen posts, the keys don’t matter very much. As the site grows the keys start to matter, a lot. Database management systems are designed to have their keys updated, adjusted, and tweaked as their tables grow. They’re designed to allow the keys to evolve without changing the content of the underlying tables. In organizations with large databases adding, dropping, or altering keys doesn’t change the underlying data. It is a routine maintenance task in many data centers. If changing keys caused databases to lose data, the MySQL and MariaDB developers would hear howling not just from you and me, but from many heavyweight users. (You should still back up your WordPress instance of course.)</p>
<p>Better keys allow WordPress’s code to run faster <em>without any code changes</em>.  Experience with large sites shows that many MySQL slowdowns can be improved by better keys. Code is poetry, data is treasure, and database keys are grease that makes code and data work together smoothly.</p>
<h4>Which tables does the plugin add keys to?</h4>
<p>This plugin adds and updates keys in these WordPress and WooCommerce tables.</p>
<ul>
<li>wp_comments</li>
<li>wp_commentmeta</li>
<li>wp_posts</li>
<li>wp_postmeta</li>
<li>wp_termmeta</li>
<li>wp_users</li>
<li>wp_usermeta</li>
<li>wp_options</li>
<li>wp_wc_orders_meta</li>
<li>wp_woocommerce_order_itemmeta</li>
<li>wp_automatewoo_log_meta</li>
</ul>
<p>You only need run this plugin once to get its benefits.</p>
<h4>How can I monitor my database’s operation?</h4>
<p>On the Index MySQL page (from your Tools menu on your dashboard), you will find the “Monitor Database Operations” tab. Use it to request monitoring for a number of minutes you choose.</p>
<p>You can monitor</p>
<ul>
<li>either the site (your user-visible pages) or the dashboard, or both.</li>
<li>all pageviews, or a random sample. (Random samples are useful on very busy sites to reduce monitoring overhead.)</li>
</ul>
<p>Once you have gathered monitoring information, you can view the captured queries, and sort them by how long they take. Or you can save the monitor information to a file and show it to somebody who knows about database operations. Or you can upload the monitor to the plugin’s servers so the authors can look at it.</p>
<p>It’s a good idea to monitor for a five-minute interval at a time of day when your site is busy. Once you’ve completed a monitor, you can examine it to determine which database operations are slowing you down the most.</p>
<p>Please consider uploading your saved monitors to the plugin’s servers. It’s how we learn from your experience to keep improving. Push the Upload button on the monitor’s tab.</p>
<h4>WP-CLI command line operation</h4>
<p>This plugin supports <a href="https://wp-cli.org/" rel="nofollow ugc">WP-CLI</a>.  When your tables are large this is the best way to add the high-performance keys: it doesn’t time out.</p>
<p>Give the command <code>wp help index-mysql</code> for details. A few examples:</p>
<ul>
<li><code>wp index-mysql status</code> shows the current status of high-performance keys.</li>
<li><code>wp index-mysql enable --all</code> adds the high-performance keys to all tables that don’t have them.</li>
<li><code>wp index-mysql enable wp_postmeta</code> adds the high-performance keys to the postmeta table.</li>
<li><code>wp index-mysql disable --all</code> removes the high-performance keys from all tables that have them, restoring WordPress’s default keys.</li>
<li><code>wp index-mysql enable --all --dryrun</code> writes out the SQL statements necessary to add the high-performance keys to all tables, but does not run them.</li>
<li><code>wp index-mysql enable --all --dryrun | wp db query</code> writes out the SQL statements and pipes them to wp db to run them.</li>
</ul>
<p>Note: avoid saving the –dryrun output statements to run later. The plugin generates them to match the current state of your tables.</p>
<h4>Why use this plugin?</h4>
<p>Three reasons (maybe four):</p>
<ol>
<li>to save carbon footprint.</li>
<li>to save carbon footprint.</li>
<li>to save carbon footprint.</li>
<li>to save people time.</li>
</ol>
<p>Seriously, the microwatt hours of electricity saved by faster web site technologies add up fast, especially at WordPress’s global scale.</p>
<h4>How can I learn more about making my WordPress site more efficient?</h4>
<p>We offer several plugins to help with your site’s database efficiency. You can <a href="https://www.plumislandmedia.net/wordpress/performance/optimizing-wordpress-database-servers/" rel="nofollow ugc">read about them here</a>.</p>
<h4>Credits</h4>
<ul>
<li>Michael Uno for Admin Page Framework.</li>
<li>Marco Cesarato for LiteSQLParser.</li>
<li>Allan Jardine for Datatables.net.</li>
<li>Leho Kraav and Sebastian Sommer for suggesting the WooCommerce tables.</li>
<li>Japreet Sethi for advice, and for testing on his large installation.</li>
<li>Rick James for everything.</li>
<li>Jetbrains for their IDE tools, especially PhpStorm. It’s hard to imagine trying to navigate an epic code base without their tools.</li>
</ul>


Index WP MySQL For Speed

Thanks for this wonderful, simple, effective and powerful plugin!

It made one of our queries 133 times faster. What a joy.

Made one of our queries 133 times faster!

This is absolutely fantastic work. I've reviewed your discussions on WP issue tracker and various other places and came to the same conclusion. While I had already added some of my own custom indexes long ago, this is even better. Amazing job!

Fantastic

Wow. Fantastic plugin! I am using the CLI to do the optimization, and within 30 seconds, all the problems with slow queries are gone! This plugin is a must-have if you have large database. :)

Fantastic plugins


I can't understand how Wordpress doesn't natively bring these indexes that speed up performance so much. Thanks to the author for this plugin.


Indexing wp should have


Great, great plugin!



Thank you for this masterpiece of software. I've optimized client's databases in seconds, changed table formats to InnoDB in seconds, and added indexes to million chains tables in minutes.



Thanks!



¡Gracias!


1.5 GB Database optimized in minutes

It's great to see a plugin like this created and maintained to such a high standard. Thank you Ollie

Top class


My WordPress-powered sites aren't popular and don't have a lot of posts yet. Still, I noticed a difference in speed immediately.


Impressive


We've used this plugin on a few busy woocommerce websites and the result is amazing.



MySQL cpu usage and response times drop dramatically. Especially if used with object cache.



Thanks again!


Amazing Results

Speed up your WordPress site by adding high-performance keys (database indexes) to your MariaDB / MySQL database tables.

Will Jackson

<p>Audit Export is a comprehensive WordPress plugin designed to help site administrators and developers analyze and report on the entity structure and overall usage of their WordPress site. The plugin provides detailed audits of various WordPress components and allows you to export this data in multiple formats.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Comprehensive Site Auditing</strong>: Analyze plugins, themes, content types, taxonomies, menus, widgets, users & roles, and generate overall site reports</li>
<li><strong>Multiple Export Options</strong>: Export audit reports as CSV files or store them in the database</li>
<li><strong>Remote Posting</strong>: Send audit data to remote endpoints with authentication support</li>
<li><strong>WP-CLI Integration</strong>: Full command-line interface for all plugin operations</li>
<li><strong>Automated Processing</strong>: Schedule audits to run automatically via WordPress cron</li>
<li><strong>Extensible Architecture</strong>: Hook-based system for adding custom audits and modifying behavior</li>
</ul>
<h4>Available Audits</h4>
<ul>
<li><strong>Plugins Audit</strong>: Lists all installed plugins with status, version, and metadata</li>
<li><strong>Themes Audit</strong>: Reports on installed themes and their configurations</li>
<li><strong>Content Types Audit</strong>: Analyzes custom post types and their usage</li>
<li><strong>Taxonomies Audit</strong>: Reviews all taxonomies including custom ones</li>
<li><strong>Menus Audit</strong>: Examines navigation menu structures</li>
<li><strong>Widgets Audit</strong>: Audits widget areas and active widgets</li>
<li><strong>Users & Roles Audit</strong>: Reports on user accounts and role assignments</li>
<li><strong>Site Report</strong>: Comprehensive overview of the WordPress installation</li>
</ul>
<h4>Export Capabilities</h4>
<ul>
<li>Save reports to the WordPress database</li>
<li>Export as CSV files to the filesystem</li>
<li>Send data to remote endpoints via HTTP POST</li>
<li>Support for JSON and CSV formats</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li><strong>Site Documentation</strong>: Generate comprehensive documentation of your WordPress site structure</li>
<li><strong>Migration Planning</strong>: Analyze site components before migrations</li>
<li><strong>Development Workflows</strong>: Track changes in site structure over time</li>
<li><strong>Client Reporting</strong>: Provide detailed site analysis reports to clients</li>
<li><strong>Multi-site Management</strong>: Centralize reporting from multiple WordPress installations</li>
</ul>
<h3>WP-CLI Integration</h3>
<p>The plugin provides comprehensive WP-CLI commands for all operations:</p>
<h4>List Available Audits</h4>
<pre><code>wp audit-export list
</code></pre>
<p>Shows all available audit reports with their ID, group, description, type, and last processed date.</p>
<h4>Run Audits</h4>
<pre><code>wp audit-export run [<audit_id>] [--all] [--format=<format>]
</code></pre>
<p>Examples:<br />
* <code>wp audit-export run</code> – Interactive audit selection<br />
* <code>wp audit-export run --all</code> – Process all audits<br />
* <code>wp audit-export run site_report</code> – Run specific audit<br />
* <code>wp audit-export run content_types --format=csv</code> – Run audit with specific output format</p>
<h4>Export Audits</h4>
<pre><code>wp audit-export export <audit_id> [--file=<file>] [--format=<format>]
</code></pre>
<p>Examples:<br />
* <code>wp audit-export export site_report</code> – Export to stdout<br />
* <code>wp audit-export export content_types --file=content_types.csv</code> – Export to file<br />
* <code>wp audit-export export plugins --format=json --file=plugins.json</code> – Export as JSON</p>
<h4>Manage Cron</h4>
<pre><code>wp audit-export cron <action>
</code></pre>
<p>Actions:<br />
* <code>status</code> – Show cron status and next run time<br />
* <code>enable</code> – Enable cron processing<br />
* <code>disable</code> – Disable cron processing<br />
* <code>run</code> – Manually trigger cron execution<br />
* <code>schedule</code> – Schedule cron events</p>
<h4>Test Remote Connection</h4>
<pre><code>wp audit-export test-connection
</code></pre>
<p>Tests the configured remote endpoint connection.</p>
<h4>Force Remote Post</h4>
<pre><code>wp audit-export force-post <audit_id>
</code></pre>
<p>Manually post a specific audit to the remote endpoint.</p>
<h4>Plugin Information</h4>
<pre><code>wp audit-export info
</code></pre>
<p>Displays plugin version, statistics, and configuration status.</p>
<h3>Configuration</h3>
<h4>File Export Settings</h4>
<ul>
<li><strong>Save to Filesystem</strong>: Enable/disable saving exports to files</li>
<li><strong>Filesystem Type</strong>: Choose between uploads directory or content directory</li>
<li><strong>Export Path</strong>: Subdirectory path for saving export files</li>
</ul>
<h4>Cron Settings</h4>
<ul>
<li><strong>Enable Cron</strong>: Turn on automated audit processing</li>
<li><strong>Run on Every Cron</strong>: Process audits on each WordPress cron execution</li>
<li><strong>Cron Frequency</strong>: Set interval in minutes (if not running on every cron)</li>
<li><strong>Queue Timeout</strong>: Maximum processing time per audit in seconds</li>
</ul>
<h4>Remote Post Settings</h4>
<p>Basic Settings:<br />
* <strong>Enable Remote Post</strong>: Turn on posting to remote endpoints<br />
* <strong>Remote URL</strong>: Endpoint URL for receiving audit data<br />
* <strong>Site Name</strong>: Identifier for this WordPress site</p>
<p>Authentication:<br />
* <strong>Authentication Type</strong>: None, Basic, or Bearer Token<br />
* <strong>Username/Password</strong>: For Basic Authentication<br />
* <strong>Bearer Token</strong>: For token-based authentication</p>
<p>Advanced:<br />
* <strong>Timeout</strong>: Request timeout in seconds (30-900)<br />
* <strong>Verify SSL</strong>: SSL certificate verification<br />
* <strong>Debug Mode</strong>: Enable detailed logging</p>
<h3>Hooks and Filters</h3>
<h4>Actions</h4>
<ul>
<li><code>audit_export_complete</code> – Fired after an audit completes processing</li>
<li><code>audit_export_before_process</code> – Fired before processing an audit</li>
<li><code>audit_export_after_process</code> – Fired after processing an audit</li>
</ul>
<h4>Filters</h4>
<ul>
<li><code>audit_export_post_url</code> – Modify the remote post URL</li>
<li><code>audit_export_post_data</code> – Modify data before remote posting</li>
<li><code>audit_export_post_site_info</code> – Customize site information in remote posts</li>
<li><code>audit_export_post_request_args</code> – Modify HTTP request arguments</li>
<li><code>audit_export_{audit_id}_headers</code> – Customize CSV headers for specific audits</li>
<li><code>audit_export_{audit_id}_data</code> – Modify audit data before saving</li>
</ul>
<h3>Developer Documentation</h3>
<h4>Creating Custom Audits</h4>
<p>To create a custom audit:</p>
<ol>
<li>Extend the <code>Audit_Export_Audit</code> abstract class</li>
<li>Implement required methods: <code>prepare_data()</code> and <code>process_data()</code></li>
<li>Set audit properties: <code>$label</code>, <code>$description</code>, <code>$group</code>, <code>$data_type</code></li>
<li>Register with the audit manager using the <code>audit_export_register_audits</code> action</li>
</ol>
<p>Example:</p>
<pre><code>class My_Custom_Audit extends Audit_Export_Audit {
    protected $label = 'My Custom Audit';
    protected $description = 'Audits custom functionality';
    protected $group = 'custom';

    public function prepare_data() {
        // Return array of items to process
    }

    public function process_data( $item ) {
        // Process individual item and return data row
    }
}
</code></pre>
<h4>Database Structure</h4>
<p>The plugin creates a table <code>{prefix}_audit_export_reports</code> with columns:<br />
* <code>id</code> – Primary key<br />
* <code>audit_name</code> – Audit identifier<br />
* <code>audit_data</code> – JSON-encoded audit results<br />
* <code>created_at</code> – Timestamp<br />
* <code>created_by</code> – User ID</p>
<h3>Support</h3>
<p>For bug reports and feature requests, please use the <a href="https://wordpress.org/support/plugin/audit-export/" rel="ugc">plugin support forum</a>.</p>
<h3>Privacy Policy</h3>
<p>This plugin stores audit data in your WordPress database and optionally saves CSV files to your server. When remote posting is enabled, audit data is sent to configured external endpoints. No data is sent to third parties without explicit configuration.</p>


Audit Export

Audits and exports WordPress site structure: plugins, themes, content types, users, menus, widgets, and taxonomies with remote posting.

Index WP MySQL For Speed vs Audit Export