Editing WoW:World of Warcraft API (section)

=== Script Profiling ===
Note: CPU profiling is disabled by default since it has some overhead. CPU profiling is controlled by the scriptProfile CVar, which persists across sessions, and takes effect after a UI reload. Memory profiling is always available. These functions were added in Patch 2.1.

:{{id|API|GetAddOnCPUUsage}}(index or "name") - Returns the total time used by the specified AddOn. This returns a cached value calculated by UpdateAddOnCPUUsage().
:{{id|API|GetAddOnMemoryUsage}}(index or "name") - query an addon's memory use (in K, precision to 1 byte) - This returns a cached value calculated by UpdateAddOnMemoryUsage().
:{{id|API|GetEventCPUUsage}}(["event"]) - Returns the time used and number of times the specified event has been triggered. If 'event' is omitted, the time and count will be totals across all events.
:{{id|API|GetFrameCPUUsage}}(frame[, includeChildren]) - Returns the time used and number of function calls of any of the frame's script handlers. If 'includeChildren' is true or omitted, the time and call count will include the handlers for all of the frame's children as well.
:{{id|API|GetFunctionCPUUsage}}(function[, includeSubroutines]) - Returns the time used and number of times the specified function was called. If 'includeSubroutines' is true or omitted, the time includes both the time spent in the function and subroutines called by the function. If it is false, then time is only the time actually spent by the code in the function itself.
:{{id|API|GetScriptCPUUsage}}() - Returns the total time used by the scripting system
:{{id|API|ResetCPUUsage}}() - Reset all CPU profiling statistics to zero.
:{{id|API|UpdateAddOnCPUUsage}}() - Scan through the profiling data and update the per-addon statistics
:{{id|API|UpdateAddOnMemoryUsage}}() - Scan through memory profiling data and update the per-addon statistics