tombenner

MySQL Profiler displays debugging information about SQL queries to admin WordPress users. For each query, the profiler displays the time, syntax-highlighted SQL, and a trace of the functions (as well as the file and line number that the functions were called from) that were called.
The list can be sorted by any of its columns, so you can, for example:
<ul>
<li>Order the list by ID to see the chronological order of the queries</li>
<li>Order the list by time to see the slowest queries</li>
<li>Order the list by query to group the queries by type (SELECT, UPDATE, etc)</li>
<li>Order the list by trace to group the queries by similar origins</li>
</ul>
The list can also filtered by typing in the search box, so you can, for example:
<ul>
<li>View all queries that use the wp_posts table</li>
<li>View all queries that are related to the use of a function in taxonomy.php</li>
<li>View all queries that are related to the use of a specific function or class</li>
<li>View all queries that call a specific MySQL function</li>
</ul>
To turn off syntax highlighting, put the following in wp-config.php:
<pre><code>define('MP_HIGHLIGHT_SYNTAX', false);
</code></pre>
To omit the file and line number from the function trace and display the functions as a comma-separated list (to save vertical space), define the following in wp-config.php:
<pre><code>define('MP_DISPLAY_FILES', false);
</code></pre>
This plugin was loosely based on <a href="http://bueltge.de/" rel="nofollow ugc">Frank Bueltge</a>‘s <a href="https://wordpress.org/extend/plugins/debug-queries/" rel="ugc">Debug Queries</a> plugin, so a hearty thanks to him for the development of that.
If you’d like to grab development releases, see what new features are being added, or browse the source code please visit/follow the <a href="http://github.com/tombenner/mysql-profiler" rel="nofollow ugc">GitHub repo</a>.

MySQL Profiler

Displays a list of each page's SQL queries and the functions calling them that can be searched and sorted by time, type, etc.

Perfbase

Perfbase profiles WordPress applications and sends performance traces to the Perfbase APM platform. It captures request lifecycle timing, WordPress context, selected metadata, and trace data through the native Perfbase PHP extension and the shared Perfbase PHP SDK.
This plugin is a Software-as-a-Service integration. It requires a Perfbase account, a Perfbase API key, and the native <code>ext-perfbase</code> PHP extension. The plugin does not submit traces until profiling is enabled and an API key is configured.
The plugin can profile:
<ul>
<li>Standard HTTP requests.</li>
<li>Admin requests when enabled.</li>
<li>AJAX requests.</li>
<li>WordPress cron runs.</li>
<li>WP-CLI commands when enabled.</li>
<li>WordPress, theme, plugin, REST, and WooCommerce context when available.</li>
</ul>
For privacy and cardinality control, request URLs are stored without query strings. Important WordPress query parameters are stored separately where useful.
<h3>External Services</h3>
This plugin connects to the Perfbase APM platform, an external application performance monitoring service, when profiling is enabled.
Service name: Perfbase APM platform and the configured Perfbase ingest API endpoint. The default endpoint is <code>https://ingress.perfbase.cloud</code>.
Service policies: <a href="https://perfbase.com/privacy/" rel="nofollow ugc">Perfbase Privacy Policy</a> and <a href="https://perfbase.com/terms/" rel="nofollow ugc">Perfbase Terms</a>.
When data is sent: trace data is sent only after a Perfbase API key is configured, profiling is enabled, the request passes the configured sampling rate, include/exclude filters, user-agent exclusions, request-type toggles, and HTTP status-code rules. For HTTP, AJAX, cron, and WP-CLI lifecycles, submission normally happens at the end of the lifecycle or during shutdown. The plugin does not submit profiling traces while profiling is disabled or while no API key is configured.
Perfbase can send:
<ul>
<li>Native trace payloads: function call trees, function names, source file paths and line numbers, timing, CPU, memory, host resource metrics, call context, and runtime error or exception context.</li>
<li>System/resource data: host operating system, kernel, hostname, CPU architecture, CPU details, disk capacity details, memory usage, CPU usage, disk I/O, and network I/O samples.</li>
<li>Process-list tracking when enabled: capped process snapshots with process ID, executable basename, OS user, CPU usage, memory usage, and process runtime. Command-line arguments are not included in process snapshots.</li>
<li>Additional native trace metadata: normalized SQL query text and query type, database DSN/host/database/username/port metadata, MongoDB or Elasticsearch query/filter payload summaries, Redis or Memcached keys and fields, HTTP URL or URI metadata that may include query strings depending on the PHP API or HTTP library used, HTTP method/status/timing/byte-count metadata, file paths and file operation metadata, mail recipient and subject metadata, shell/process command strings, AWS operation names, OPcache and JIT statistics, PHP error or exception samples, compiled file paths, magic method counts, and truncated function argument values if argument capture is separately configured.</li>
<li>WordPress request metadata: action name, HTTP method, request URL without query string, HTTP status code, user IP address, user agent, logged-in user ID when available, hostname, environment, application version, PHP version, WordPress version, and Perfbase plugin version.</li>
<li>WordPress context metadata: AJAX action, REST route, admin page, post/page identifiers, post type/status, taxonomy context, template and theme information, conditional page type flags, plugin lifecycle context, and WooCommerce page, cart, product, or order context when available.</li>
<li>Operational summaries: memory usage, database query count and timing summaries when available, and sanitized outbound HTTP request metadata when HTTP tracking is enabled.</li>
</ul>
Perfbase does not collect:
<ul>
<li>Source code.</li>
<li>Request bodies, full POST payloads (<code>$_POST</code>), arbitrary form fields, or uploaded file contents.</li>
<li>Cookie values (<code>$_COOKIE</code>) or PHP session data (<code>$_SESSION</code>).</li>
<li>Authorization header values.</li>
<li>Passwords, API keys, nonces, or session IDs from WordPress request, cookie, or session data.</li>
<li>Command-line arguments for process-list snapshots.</li>
</ul>
Feature flags control the extra native trace metadata listed under “Perfbase can send”, including outbound HTTP URLs or URIs with query strings for some HTTP libraries and truncated function argument values if argument capture is separately configured. Administrators should review enabled Perfbase extension feature flags before profiling sensitive workloads.
Extension installer and CDN: the plugin runtime does not call <code>cdn.perfbase.com</code>. The optional extension installer and manual extension binary downloads use <code>https://cdn.perfbase.com</code> only when a server administrator downloads or runs those installation assets.
<h3>Privacy</h3>
This plugin connects to Perfbase’s external service when profiling is enabled. It sends profiling trace data and request metadata to the configured Perfbase API endpoint.
Data submission requires explicit configuration of a Perfbase API key and the Enable Profiling setting. The plugin does not submit traces while profiling is disabled or while no API key is configured.
Administrators should review their site’s privacy policy and disclose their use of Perfbase where appropriate.

WordPress integration for the Perfbase APM platform.

MySQL Profiler vs Perfbase