• Resolved forgetme

    (@forgetme)


    In your FAQ you mention the info below, is this for all website visitors or only when an Admin is logged in? If it is everyone is there a way to restrict this to only when an Admin is logged in since the info shown seems to primarily serve for debugging slow points.

    Does Query Monitor itself impact the page generation time or memory usage?
    Short answer: Yes, but only a little.

    Long answer: Query Monitor has a small impact on page generation time because it hooks into WordPress in the same way that other plugins do. The impact is low; typically between 10ms and 100ms depending on the complexity of your site.

    Query Monitor’s memory usage typically accounts for around 10% of the total memory used to generate the page.

Viewing 1 replies (of 1 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    This applies to all page requests, but to a lesser degree for non logged in users or users who cannot view QM.

    Query Monitor separates its data collection, which is collected for all users, from the processing that it needs to do of the data, which only happens for logged in users who can view QM. How much of an impact this has entirely depends on how many database queries are being performed, whether translation files are loaded, whether there are many hooks being fired, etc.

Viewing 1 replies (of 1 total)
  • The topic ‘Does Query Monitor impact performance for customers?’ is closed to new replies.