You should utilize the historical past view function to do plenty of various things:

  • Intuitively perceive the efficiency tendencies of probably the most resource-intensive features over time

  • Uncover unintended useful resource utilization adjustments. Giant-scale or advanced code adjustments can have unintended useful resource utilization implications. Trying on the historical past view, you possibly can confirm that your code adjustments didn’t introduce unintended efficiency or useful resource utilization adjustments.

  • Confirm the efficiency impression of latest code adjustments.

  • Quickly discover the basis explanation for an outage of extreme efficiency regression. If a service has stalled as a result of excessive CPU or reminiscence consumption, trying on the historical past of every operate’s useful resource consumption will present perception into when and what elements of the code lately began utilizing extra assets.

  • Characterize how a codebase’s efficiency adjustments as a result of exterior components resembling utilization spikes (this may also be visualized with Profiler’s weight filter) or identified adjustments in utilization patterns.

Profiler historical past view is out there instantly as a preview for all customers. Read extra about the way to use this function.

If you’re new to Profiler, our Quickstart or codelab may also help you get began.

Leave a Reply

Your email address will not be published. Required fields are marked *