|
Using Siebel Tools > Using Siebel Script Editors > Using the Script Profiler >
Overview of the Script Profiler
The Siebel Script Performance Profiler is a part of the ST eScript Engine that allows you to observe and monitor the performance of a script. For brevity, this guide refers to the Siebel Script Performance Profiler as the Script Profiler. If you start Siebel CRM in debug mode from Siebel Tools, then the Script Profiler gathers and displays data for all executable scripts. It displays data in the Script Performance Profiler window in Siebel Tools and updates this data if a script runs. You can use this data to monitor script performance, identify performance bottlenecks, and compare performance with previous script runs. The Script Profiler allows you to do the following:
- Use the Call Tree view. Displays profile data as a tree of function calls. For more information, see Example of the Script Performance Profiler Window.
- View function profile and line profile. Line profile data includes the call count and total time spent for each line that runs in a function. Line profile information is available only for a compiled script and is not available for a line that does not run.
- Save profile data to file. You can save profile data that the Script Performance Profiler window shows to a text file.
- Use the Siebel Script Debugger and the Siebel Script Profiler. You can use the Script Profiler and the Script Debugger at the same time. Profile data is consistent even if the function uses Debugger functionality, such as a breakpoint.
- View the script source. Siebel Tools opens the objects that a script references in the Script Editor window. You can double-click a function name or line number to view the script from the Script Performance Profiler window. The View Source option is available only for a compiled script. It is not available for a runtime script.
Example of the Script Performance Profiler Window
Figure 6 displays an example of the Script Performance Profiler window. It allows you to examine script performance. It displays a line number for each code line, total time spent to run that line, the number of times Siebel CRM runs the line, and so on.
Figure 6. Example of the Script Performance Profiler Window
|
Description of the Columns in the Script Performance Profiler Window Table 13 describes the columns that the Performance Profiler window includes. For the Source Line, Call Count, and Total Time columns, if line profiling is enabled for a function, then the line profile displays as child nodes of a function in the Call Tree view and in the Flat Profile view.
Table 13. Description of Columns in the Script Performance Profiler Window
|
|
Function/Source Line |
Function name and the name of the object that contains the function. For example: Service [ATP Check]::service_preinvokeMethod and BusComp[Account]::foo
|
Call Count |
The number of times Siebel CRM calls a function. You can use one of the following views:
- Flat Profile view. Displays the total number of times Siebel CRM calls the function.
- Call Tree view. Displays the number of times Siebel CRM calls the function in the current position in the call tree. It displays profile data as a tree of function calls. A node represents each function in a call sequence. You can drill down into each node to examine a subtree. You can use the Expand All option in the Profiler toolbar to expand all nodes.
|
Total Time |
Total milliseconds spent in this function and in nested functions. |
Max Time |
Maximum milliseconds spent in this function and in nested functions. |
Min Time |
Minimum milliseconds spent in this function and in nested functions. |
Total Self Time |
The total milliseconds spent in the current function, not including time spent in the subtree of this function. |
Max Self Time |
The maximum milliseconds spent in the current function, not including time spent in the subtree of this function. |
Min Self Time |
The minimum milliseconds spent in the current function, not including time spent in the subtree of this function. |
|
