Code Profiler results are sorted in descending order by the sum of total elapsed times. This provides a quick overview of where time is spent.

The table of results includes:

- Type - the kind of artifact being measured
- Name - the specific artifact being measured
- Hits - the number of invocations of the
artifact that have been measuredNote: Because Production Mode only measures a subset of all requests, this number might not represent the total number of invocations.
- Time, which is measured in two different ways:
- Elapsed Time - the time spent executing the given artifact
- Wait Time - subset of Elapsed Time that is not spent processing, such as I/O operations (database or service calls) or concurrency-related locking

- For Elapsed Time and Wait Time, there is also data to indicate:
- Own Time - the time spent exclusively by the given measurement frame, subtracting runtimes of enclosed frames
- Total Time - total duration between the beginning and the end of the result's execution

- For Own Time and Total time, the following is provided:
- Sum - the total amount of all measured
runtimes for the given resultNote: Sum times in Production Mode only represent runtimes in the measured subset of requests.
- Average - the mean runtime given by Sum divided by Hits

- Sum - the total amount of all measured
runtimes for the given result