Ipower web hosting - CHAPTER 10 JAVA EE PERFORMANCE ASSESSMENT Nonprecompiled
CHAPTER 10 JAVA EE PERFORMANCE ASSESSMENT Nonprecompiled JSP In an MVC-based Web architecture, the standard process is to implement a controller servlet that handles incoming requests. The front-controller servlet (Controller) interacts with business functions that build resultant beans (Model) containing the results of the request, and those results are forwarded to a JSP for presentation (View). In this type of environment, if the JSP is not currently compiled, when the RequestDispatcher s forward()method is called, the application server must go through a three-step process before executing the JSP functionality: 1. It must convert the JSP to servlet source code; it builds a .java source code file. 2. It must compile the servlet into bytecode; it builds a .class file. 3. It loads the .classfile into permanent memory and creates an instance in the heap to handle the request. When this process occurs, from a bytecode instrumentation perspective, the RequestDispatcher.forward() method takes extra time to process. If the JSP is already compiled, then this method should have close to zero exclusive time, but if not, then this method can contribute greatly to the overall response time of the request. SQL Report The most accurate assessment of database performance health is best performed by database monitoring software, but you can learn a lot about how database queries affect the performance of Java EE applications. By using bytecode instrumentation, you can learn the following, for example: The number of unique SQL statements executed by an application A list of all SQL executed by an application The number of times each SQL statement was executed The average response time for each SQL statement The maximum response time for each SQL statement The total response time for each SQL statement A breakdown of the time spent in preparation, execution, and retrieval for each SQL statement The service requests that were affected by each SQL statement The SQL report serves these purposes: Identifies problematic SQL to send to DBAs for troubleshooting Determines the number of unique SQL statements executed to best size the prepared statement cache Maps SQL statements to the requests that execute them
We recommend high quality webhost to host and run your jsp application: christian web host services.