Missing Time in Widget Logs
Posted: May 18th, 2022, 10:05 pm
There are many times where a widget logs a longer duration than all of the related processes combined. In this example, there is 150ms unaccounted for in the logs, and I've seen this compound when several widgets exist on a page at once. I assume this is due to some HTML generation going on in the backend, but I don't know that for sure. Is there any way that the time added by this overhead can be captured and added to the logs?