Performance Issue with Query Monitor Plugin on Admin Pages

  • Resolved Nirav

    (@niravcse006)


    5 months, 2 weeks ago

    Hello Support,

    We are currently experiencing performance issues on our WordPress site when using the Query Monitor plugin.

    The site is running smoothly with multiple plugins activated and overall backend performance is excellent when accessing posts or pages. However, when Query Monitor is active, the page and post editor load times are significantly slower, and at times, the screen freezes or becomes unresponsive while editing content.

    We checked the error logs and found the following error related to the Query Monitor plugin:

    Error: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /wp-content/plugins/query-monitor/collectors/db_dupes.php on line 98

    It appears that Query Monitor is consuming excessive memory, particularly when working within the admin editor. This issue does not occur when the plugin is disabled.

    Could you please investigate this and let us know:

    • Why the Query Monitor plugin is generating such high memory usage?
    • Is there a way to limit or optimize its memory consumption?
    • Can we exclude or disable Query Monitor on specific admin pages (like post/page editors) to prevent these issues?

    Your guidance would be greatly appreciated.

    Thank you

    • This topic was modified 5 months, 2 weeks ago by Nirav.
Viewing 1 replies (of 1 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    5 months, 1 week ago

    This is a known issue on sites which are already performing especially poorly and are close to their memory limit. It’s ironic, I know. If a site is low on free memory and performs a large number of database queries, HTTP API requests, or loads a large number of translation files, then it’s entirely possible for QM to push it over the memory limit due to its data collection.

    The quick fix is to increase the PHP memory limit, although I appreciate this isn’t always possible.

    Regarding the screen freezing, this depends on how resource constrained your browser is. If you’re regularly seeing freezes then I suspect your site is performing a huge number of database queries, which causes the browser to lag. I’ll hopefully address this in the future by changing the way that the data tables are rendered but I don’t have an ETA for now.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.