ESI Summary | SQL profiling
Profiling
Profiling is a technique that can be used at any phase of a project life cycle. During the development phase it can be used by developers to pinpoint areas in their code that might have performance implications. In this way performance issues can be addressed early on, resulting in incredible savings in time, effort, and money. Therefore, it is extremely important that the developers have the responsibility of profiling their own code in their development environment first, before any performance testing phases are started. Profiling can also be used during the performance load test phase to drill down on areas highlighted as having poor response times.
When assessing the performance of a single page, developers will find the following four exercises incredibly rewarding in quickly identifying the performance bottlenecks:
- Use IBM Page Detailer to get an overall idea of how fast the page loads and how long it takes to render each page element to the browser.
- Conduct SQL profiling to capture expensive or excessive database queries. Then either eliminate the unnecessary SQLs or tune the expensive SQLs to improve performance.
- Conduct Java code profiling to identify bottlenecks in the code and revise to improve performance.
- If necessary, apply techniques to map SQL statements to Java code in WebSphere Commerce.