Andrew Sondgeroth

I discussed many of the views in the Profiling Perspective of IBM's WebSphere Studio Application Developer (WSAD) 5.0 in Part 1 of this series, which focused on understanding the information displayed in the different views. In this article I will discuss code optimization and how to use WSAD to pinpoint areas of your applications that need performance tuning. The Purpose of Profiling To recap the explanation in Part 1, profiling is used to inspect the performance of code. Profiling allows analysis of application behavior for improving application efficiency. Profiling an application can also provide detection of major architectural problems early in the development life cycle. Profiling helps identify many behaviors and problems, including: Memory leaks/inefficient memory usage Poor method response times Frequent code block usage ("hot spots") Threading issues Optimi... (more)

Profiling in WebSphere Studio 5.0

IBM's goliath enterprise tool, WebSphere Studio Application Developer (WSAD) 5.0, has a powerful, full-featured profiling toolset for developers. However, learning how to use the tools and how to interpret the information takes some time. In Part 1 of this two-part series, I will focus on understanding the information presented by the WSAD 5.0 profiling tools. In Part 2 (in an upcoming issue), I will discuss how to optimize and fix code using the gathered information. The Purpose of Profiling In some ways, profiling is similar to debugging. Both are used to examine application ... (more)