Skip Headers

# Measuring TopLink Performance With the TopLink Profiler

Previous

Next

The most important challenge to performance tuning is knowing what to optimize. To improve the performance of your application, identify the areas of your application that do not operate at peak efficiency. The TopLink performance profiler helps you identify performance problems by logging performance statistics for every executed query in a given session.

Note: You should also consider using general performance profilers such as JDeveloper or JProbe to analyze performance problems. These tools can provide more detail that may be required to properly diagnose a problem.

The TopLink performance Profiler logs the following information to the TopLink log file (for general information about TopLink logging, see "Logging"):

- Query class

- Domain class

- Total time, total execution time of the query (in milliseconds)

- Local time, the amount of time spent on the user's workstation (in milliseconds)

- Number of objects, the total number of objects affected

- Number of objects handled per second

- Logging, the amount of time spent printing logging messages (in milliseconds)

- SQL prepare, the amount of time spent preparing the SQL script (in milliseconds)

- SQL execute, the amount of time spent executing the SQL script (in milliseconds)

- Row fetch, the amount of time spent fetching rows from the database (in milliseconds)

- Cache, the amount of time spent searching or updating the object cache (in milliseconds)

- Object build, the amount of time spent building the domain object (in milliseconds)

- Query prepare, the amount of time spent to prepare the query prior to execution (in milliseconds)

- SQL generation, the amount of time spent to generate the SQL script before it is sent to the database (in milliseconds)

This section includes information on the following topics:

- Configuring the TopLink Performance Profiler

- Accessing the TopLink Profiler Results

See Also

  Optimization
  Understanding Optimization