Exclusive Clock Method Time divided by the number of calls to the method. This is the average time spent within the method.
Related Topics
•Inclusive Versus Exclusive Time (page 69)
•Mark an Item for Search (page 178)
•Find a Search Pattern (page 179)
Average Inclusive Method CPU Times*Inclusive CPU Method Time divided by the number of calls to the method. This gives the average CPU cost for a
Related Topics
•Inclusive Versus Exclusive Time (page 69)
•Mark an Item for Search (page 178)
•Find a Search Pattern (page 179)
Average Inclusive Method Clock Times*Inclusive Clock Method Time divided by the number of calls to the method. This gives the average
Related Topics
•Inclusive Versus Exclusive Time (page 69)
•Mark an Item for Search (page 178)
•Find a Search Pattern (page 179)
Starvation by Method*Shows the starvation for each method. For our purposes, starvation is defined as time unaccounted for. During this time, the thread was not suspended by java.lang.Thread.sleep or java.lang.Object.wait, and it was not delayed at the monitor lock entry. The thread was runnable (in the Java sense), yet it was not running; that is, the context had switched out.
These are possible reasons for reported starvation:•the real starvation caused by the operating system scheduler - this should be distributed over all methods in proportion to the exclusive CPU time consumed by each method
•waiting for the class loader to load a class•waiting on an internal VM lock (mutex)•time consuming system calls•explicit or implicit Garbage Collection invocation (frequent or massive memory allocation by the method)
•excessive virtual memory paging•suspending the thread by external means (i.e. by a debugger)Related Topics
•Inclusive Versus Exclusive Time (page 69)
Using Profile Displays 143