Impact for non-admin hits

  • I see there’s a FAQ that deals with the question of whether this plugin has much impact on site performance for logged-in admin users, but I’m curious about the case where a normal visitor hits a page. Is there any measurable overhead in that case? Does the plugin really even fire for non-admins?

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

    (@johnbillion)

    WordPress Core Developer

    Yeah QM always collects data but doesn’t do any processing of it unless the current user can view the output.

    It’s a difficult question to answer, QM’s impact mostly depends on how many database queries, actions, PHP errors, capability checks, transients, etc that your site is firing.

    If your site is performing a thousand database queries and triggering a hundred PHP errors then QM will use more memory, but in that case you need to look at other optimisations anyway.

    If you’ve got full page caching then there’s nothing to be concerned about for non logged in users.

    Thread Starter sporkme

    (@sporkme)

    Thanks. I had a hosting company pointing the finger at this and while I’m on the fence about running QM in production, I generally find the info it provides is worth more than the performance impact. The hosting provider was asserting that QM was not a root cause for performance issues, but definitely something to look at, and I was a little suspicious of that.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Impact for non-admin hits’ is closed to new replies.