Payload size

  • Resolved patrickwgs

    (@patrickwgs)


    2 years, 9 months ago

    First of all, thank you for that invaluable tool. I don’t know what I’d do without it, so thanks 🙂

    I’ve noticed that in some cases the HTML payload is absolutely enormous. I can see 8MB or more. In some cases I’ve seen a 20MB + payload.

    I’m guessing it’s just on big sites, there is so much to log it makes sense.

    Is there a way to truncate the log – or do partial logging, when the response becomes too big?

    Thank you!

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

    (@johnbillion)

    WordPress Core Developer

    2 years, 9 months ago

    Yeah it’s quite easy for the HTML itself to run into the MB on a heavy site, I’m working on alleviating this by switching to client-side rendering in https://github.com/johnbillion/query-monitor/pull/483 but it won’t be ready soon.

    There’s no way to do partial logging but you can instruct QM to stop its collection and processing midway through the page load by calling do_action( 'qm/cease' ). Useful for long-running processes.

    Unfortunately I can’t be of much more help. I hope your browser survives.

    Thread Starter patrickwgs

    (@patrickwgs)

    2 years, 9 months ago

    Ok thank you! I’ll see how I can leverage that 🙂

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Payload size’ is closed to new replies.