Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/UserGuide/JPA/Advanced JPA Development/Performance"

m (EclipseLink Performance)
m
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
----
 +
 +
 +
'''[[Image:Elug_draft_icon.png|Warning]] This page is now obsolete. '''
 +
 +
For current information, please see "Enhancing Performance" in the ''EclipseLink Solutions Guide'':
 +
http://www.eclipse.org/eclipselink/documentation/latest/solutions/toc.htm
 +
 +
 +
----
 +
 +
 +
{{EclipseLink_UserGuide
 +
|info=y
 +
|toc=n
 +
|eclipselink=y
 +
|eclipselinktype=JPA}}
 +
 
=EclipseLink Performance=
 
=EclipseLink Performance=
 +
 +
EclipseLink provides a diverse set of features to measure and optimize application performance. You can enable or disable most features in the descriptors or session, making any resulting performance gains global.
 +
 +
 +
 +
==Introduction to Optimization==
 +
Performance considerations are present at every step of the development cycle. Although this implies an awareness of performance issues in your design and implementation, it does not mean that you should expect to achieve the best possible performance in your first pass.
 +
 +
For example, if optimization complicates the design, leave it until the final development phase. You should still plan for these optimizations from your first iteration, to make them easier to integrate later.
 +
 +
The most important concept associated with tuning your EclipseLink application is the idea of an iterative approach. The most effective way to tune your application is to do the following:
 +
# [[EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance/Performance_Profiling|Measure EclipseLink Performance with the EclipseLink Profiler]].
 +
# [[#Identifying Sources of Application Performance Problems|Identify sources of application performance problems]] and modify application components;
 +
# Measure performance again.
 +
 +
To identify the changes that improve your application performance, modify only one or two components at a time. You should also tune your application in a nonproduction environment before you deploy the application.
 +
 +
==Identifying Sources of Application Performance Problems==
 +
For various parts of an EclipseLink-enabled application, this section describes the performance problems most commonly encountered and provides suggestions for improving performance. Areas of the application where performance problems could occur include the following:
 +
* [[#Identifying General Performance Optimization|Identifying General Performance Optimization]]
 +
* [[#Optimizing Schema|Schema]]
 +
* [[#Optimizing Mappings and Descriptors|Mappings and Descriptors]]
 +
* [[#Optimizing Sessions|Sessions]]
 +
* [[#Optimizing Cache|Cache]]
 +
* [[#Optimizing Data Access|Data Access]]
 +
* [[#Optimizing Queries|Queries]]
 +
* [[#Optimizing the Unit of Work|Unit of Work]]
 +
* [[#Optimizing the Application Server and Database Optimization|Application Server and Database Optimization]]
  
  
Line 5: Line 51:
  
 
{{EclipseLink_JPA
 
{{EclipseLink_JPA
|previous=[[EclipseLink/UserGuide/JPA/Advanced_JPA_Development/|Advanced JPA Development]]
+
|previous=[[EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Data Partitioning|Data Partitioning]]
|next=[[EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance Profiling|Performance Profiling]]
+
|next=   [[EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance/Performance Monitoring and Profiling|Performance Monitoring and Profiling]]
|up=[[EclipseLink/UserGuide/JPA/Advanced_JPA_Development|Advanced JPA Development
+
|up=     [[EclipseLink/UserGuide/JPA/Advanced_JPA_Development|Advanced JPA Development]]
}}
+
|version=2.2.0 DRAFT}}

Latest revision as of 07:36, 17 April 2013



Warning This page is now obsolete.

For current information, please see "Enhancing Performance" in the EclipseLink Solutions Guide: http://www.eclipse.org/eclipselink/documentation/latest/solutions/toc.htm




EclipseLink JPA

Eclipselink-logo.gif
EclipseLink
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse Source


EclipseLink Performance

EclipseLink provides a diverse set of features to measure and optimize application performance. You can enable or disable most features in the descriptors or session, making any resulting performance gains global.


Introduction to Optimization

Performance considerations are present at every step of the development cycle. Although this implies an awareness of performance issues in your design and implementation, it does not mean that you should expect to achieve the best possible performance in your first pass.

For example, if optimization complicates the design, leave it until the final development phase. You should still plan for these optimizations from your first iteration, to make them easier to integrate later.

The most important concept associated with tuning your EclipseLink application is the idea of an iterative approach. The most effective way to tune your application is to do the following:

  1. Measure EclipseLink Performance with the EclipseLink Profiler.
  2. Identify sources of application performance problems and modify application components;
  3. Measure performance again.

To identify the changes that improve your application performance, modify only one or two components at a time. You should also tune your application in a nonproduction environment before you deploy the application.

Identifying Sources of Application Performance Problems

For various parts of an EclipseLink-enabled application, this section describes the performance problems most commonly encountered and provides suggestions for improving performance. Areas of the application where performance problems could occur include the following:



Eclipselink-logo.gif
Version: 2.2.0 DRAFT
Other versions...

Back to the top