CHAPTER 10 JAVA EE PERFORMANCE ASSESSMENT (Web host forum) Figure
CHAPTER 10 JAVA EE PERFORMANCE ASSESSMENT Figure 10-12. The call tree color codes its nodes by the average cumulative time of each method. As Figure 10-12 illustrates, the Web server receives the request, forwards it to the Apache Struts doGet() method, which in turn calls the RequestProcessor.process() method. The popup window demonstrates that the doGet() method was a component of the hot path (because its average cumulative time was 27.276 seconds), but it is not a hot point (because its average exclusive time was less than 0.001 second). Figure 10-13 shows a view of the same request tree sorted by the average exclusive time. Figure 10-13 sorts the color coding by exclusive time, revealing that the RequestProcessor. process() method spent 13.5 exclusive processing seconds of a total of 27.7 cumulative seconds. Further investigations will reveal that this is the largest hot point within the request, but another 14.2 seconds need to be accounted for. Note This is a complicated request, and the 27.7 seconds of total response time are broken into various components. The 13.5 exclusive seconds spent inside the RequestProcessor.process() method are actually a little misleading, because the org.apache.struts.action package is grouped in a custom component, so the process() method may not have taken 13.5 seconds, but 13.5 seconds elapsed inside the org.apache.struts.action package before calling out to application code. We continue this process by identifying the next slowest node in the hot path, isolating its subtree, and finding its hot point. In this example, the next slowest method, calculateOrderTax(), accounted for almost 3 of the remaining 14.2 seconds, as shown in Figure 10-14.
We highly recommend you visit web and email hosting services if you need stable and cheap web hosting platform for your web applications.