In order to help you find JProfiler's features which are most important to you,
we present a situational overview. There are two types of uses for a profiler which
arise from different motivations:
- Problem solving
If you turn to a profiler with a problem in your application, it most likely
falls into one of the following three categories:
- Quality assurance
During a development process, it's a good idea to regularly run a profiler on your
application to assess potential problem spots. Even though an application may prove
to be "good enough" in test cases, an awareness for performance and memory bottlenecks
enables you adapt your design decisions as the project evolves. In this way you
avoid costly re-engineering when real-world needs are not met. Use the information
presented in JProfiler's telemetry section
to keep an eye on the evolution of your application.
The ability to save profiling snapshots enables
you to keep track of your project's evolution.
The offline profiling capability allows you to perform
automated profiling runs on your application.