Java Code-Level Visibility
The toughest IT performance problems to solve today are the ones where a user complains that their application access is slow. An IT administrator must then figure out the cause of the problem: is it the browser, the network, the server, the storage, the cloud infrastructure on which the application is hosted, or the application code? Determining whether the problem is in the application often requires visibility at the code level: which module, which method, which line of code is causing the problem? Slowness can result from many problems in the application code. Inefficient code, which causes excessive looping, poorly designed queries that result in long database access times, insufficient resources for the application, or external services that have slowed down can all cause application slowness. A DZone performance survey found that 43% of application performance issues are due an issue in the application code.
To troubleshoot problems quickly, IT administrators need to have code-level visibility. At the same time, developers also need the same level of visibility. After all, they need to know where to fix the issue: which module, method and line of code. Code-level visibility also helps identify why the slowness occurred – is it a spin loop, is it a synchronization issue, is it a query issue, external API call, etc.? Profiling tools can be used for providing code-level visibility, but these tools often have high overhead and cannot be used in production environments. To provide code-level visibility in production environments, a couple of approaches can be used:
Read the entire article here, Java Code-Level Visibility | eG Innovations
Via the fine folks at eG Innovations/a>.