suggested change to “Scan troubleshooting” page

  • Resolved Paul Biron

    (@pbiron)


    6 years, 7 months ago

    In the “Plugin conflicts” section of your “Scan Troubleshooting” page you recommend deactivating Query Monitor if one is having memory allocation problems while running scans.

    I suggest that you change that recommendation.

    Query Monitor (one of the go-to plugins I use on all sites I administer) supports disabling the “saving of queries” which you note can use a great deal of memory by simply adding define( 'SAVEQUERIES', false ); to wp-config.php.

    Doing so leaves in place all of the other useful diagnostic info that Query Monitor provides, while being much less memory intensive.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Paul Biron

    (@pbiron)

    Defining SAVEQUERIES = false typically reduces memory use during scans on sites I admin to 10% of usage when SAVEQUERIES = true!

    Hi @pbiron,

    Thank you for your input.

    This is indeed something our developers have previously looked into when they found out that Query Monitor was causing high memory usage during scans.

    However, it turns out that setting “SAVEQUERIES” to “false” impacts several Query Monitor features —tracking query results for duplicates, speed, displaying the list of queries run, etc..

    Thread Starter Paul Biron

    (@pbiron)

    I know, but disabling just those useful features of QM is better than deactivating the plugin altogether!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘suggested change to “Scan troubleshooting” page’ is closed to new replies.