Skip to content

drupal perf

Paulo Maia Carvalho edited this page May 20, 2026 · 1 revision

drupal-perf

Analyse performance of the Drupal installation — cache configuration, slow queries, module overhead, and bottlenecks.

Usage

/drupal-perf

What it analyses

1. Cache configuration

Checks whether aggregation is enabled for CSS and JS, and whether an external cache backend (Redis, Memcache) is configured.

drush config:get system.performance

2. Slow query log

Reads the database slow query log (if enabled) and surfaces queries exceeding the threshold. Reports query count, average time, and the top offenders.

3. Enabled modules audit

Lists all enabled modules and flags:

  • Modules typically disabled in production (e.g. devel, kint, webprofiler)
  • Modules known to have performance implications without caching (e.g. views_ui left enabled in production)

4. Views with no caching

Scans all Views and reports those with caching set to none. Uncached views are a common source of slow pages.

5. PHP OPcache status

Checks whether OPcache is enabled and reports hit rate. A low hit rate or disabled OPcache significantly degrades PHP performance.

6. Memory usage

Checks PHP memory limit and peak memory usage from recent requests (if available via the profiling log).

Output

The skill produces a prioritised list of findings:

  • Critical — items that should be addressed before going to production
  • Warning — items worth reviewing
  • Info — current configuration for reference

Notes

  • Full analysis requires the Docker stack to be running.
  • Slow query log analysis only works if slow_query_log is enabled in the database config. The skill detects this and notes if data is unavailable.

Related skills

  • drupal-status — overall project health
  • drupal-debug — error diagnosis (different from performance)
  • drupal-cr — rebuild caches as a first step for performance issues

Clone this wiki locally