getMethodProfileInfo(jdo: JadeDynamicObject input; truncated: Boolean output);
The
The retrieved information is presented as a set of dynamic objects in the children collection of the dynamic object instance specified by the jdo parameter; that is, the information is contained in the collection jdo.children.
The calling process is responsible for creating and deleting the
If the JadeDynamicObject instance used as the jdo parameter is persistent, the JadeDynamicObject instances added to the children collection are also persistent. Similarly, if the object is transient, the child dynamic objects are transient.
The properties of the
Property | Type | Description |
---|---|---|
method | Object | Reference to the Method instance for the profiled method |
calls | Integer64 | Number of times the method was called |
totalCpuTime | Integer64 | Total CPU time in microseconds consumed by the method and the methods it called |
cpuTimeInMethod | Integer64 | Total CPU time in microseconds consumed by the method only; that is, excluding time consumed by the methods it called |
totalClockTime | Integer64 | Total clock time in microseconds elapsed while executing the method and the methods it called |
clockTimeInMethod | Integer64 | Total clock time in microseconds elapsed while executing the method only; that is, excluding time elapsed while executing the methods it called |
Time spent in recursive method calls is correctly accounted for as time spent executing the method.
The truncated parameter indicates if the amount of method profile information to be retrieved exceeded an internal buffer limit so was truncated. If the truncated parameter is returned as false, all method profiling information is present in the
Truncation occurs when the amount of profiling information to be returned exceeds 1,000 entries.
Truncation occurs only when method profiling information is retrieved for processes running on remote nodes.
The CPU time has a granularity of 10 or 15 milliseconds, which means that the CPU time figures for methods of short duration are subject to inaccuracy due to the large granularity. However, the clock times have a much smaller granularity and are therefore more accurate.
Clock times may fluctuate depending on other activity on the same machine. The total clock times include time spent waiting; for example, to wait for a Window event, to lock an object, or for a user response to a modal form.
The children collection of the jdo parameter passed to the
When displaying method profiling results, you can use the qualifiedName method of the corresponding Method instance (specified in the method parameter) to obtain the name of a profiled method, and the
Any process can call the
If you call the getMethodProfileInfo method on a target process that has terminated, an exception of type 4 (
For usage and output examples of this method, see the