1. KTS915

    Query Monitor is absolutely fantastic and the first plugin I install now — having been alerted to its existence by a previous post of yours, Sarah. Thanks!

  2. Is this plugin a resource hog ? My hosting provider really frowns on plugins that take too many resources.

  3. I’ve used it for a long time and attest to it’s awesomeness. Before QM I always installed and activated Debug Bar, now I install DebugBar but I don’t activate it unless I actually need it for something (rare). QM get’s me everything I normally need.

    Come to think of it though, we need some good blog posts about actually using it for all the various things it can help diagnose…

    1. I love that idea, where would we find such an encyclopedia of intel? :D

  4. But what am I looking for?

    To my untrained eye, Query Monitor looks like it provides a wealth of information. Unfortunately, I’m not 100% what I’m looking for when I look at QM’s output.

    For example:

    Page generation time: What’s a good time score to shoot for?
    Peak memory usage: What’s average? What’s good?
    Database query time: Am I slow? What’s fast look like?
    Database queries: How many is too many? How many is awesome?


    It would be super helpful to see someone put together a basic “how to use Query Monitor” post to help people score and optimize their sites.

Comments are closed.