Profiling non-HTML requests

[szepeviktor]

trafficstars

It cannot be expressed in words how easy it is to debug and profile with QM.

Could we find a way to save all the QM output for a non-HTML request (ajax, rest, xml-rpc, anything) and display it later?

[mbellmbell]

+1 for REST profiling. QM helped me get web performance up by 10X in an hour but REST requests are still a mystery.

[pentatonicfunk]

+1 on this we already had : X-QM-overview-time_taken X-QM-overview-time_usage X-QM-overview-memory X-QM-overview-memory_usage X-QM-php_errors-error-count X-QM-php_errors-error-XXXX

Would be good if we can trace DB request and Hooks. not sure how hard it will be to implement

[johnbillion]

This is ultimately going to be enabled by #483, but it's going to take a few more months as I'm very busy at the moment.

[fronbasal]

Any update on this? @johnbillion Thank you for the amazing work!

[johnbillion]

I've been working on the client-side rendering in #483 but it's a slow-burner that I work on when I have spare time. No ETA just yet. 🤞

[fronbasal]

Thank you so much for the quick update!