Difference between revisions of "EclipseLink/Performance"

Revision as of 15:07, 31 January 2013

EclipseLink is dedicated to being the best performing, and most scalable JPA implementation.

EclipseLink's performance features include:

Object cache
- Cache invalidation (time to live, and time of day)
- Configurable cache types per Entity, (Weak, Soft, SoftCache, HardCache, Full)
- Configurable cache size per Entity
- Clustered cache coordination
Querying
- Read-only queries
- Join fetching (query, nested, mapping)
- Batch reading (query, nested, mapping)
- Fetch groups (query, default, dynamic)
- Fetch size
- Pagination (firstResult, maxResult, ROWNUM filtering)
- Cursors (stream and scrollable)
- Cache usage (in-memory, primary key)
- Query cache (invalidation, size configuration)
Mapping
- Lazy loading
- Read-only objects
- Weaving enhancements
Transactions
- Attribute level change tracking
- Field level updates
Database
- Connection pooling
- Parametrized SQL
- Statement caching
- Batch writing (JDBC, parametrized, native)
Tools
- Performance Profiler

@@ Line 40: / Line 40: @@
 ==Links==
-* [[Optimizing_the_EclipseLink_Application_(ELUG)| EclipseLink User Guide - Optimization]]
+* "Enhancing Performance" chapter in the ''[http://www.eclipse.org/eclipselink/documentation/ EclipseLink Solutions Guide]''
 * [[EclipseLink/Development/Performance | Performance Development]]
 * [http://java-persistence-performance.blogspot.com/ Java Persistence Performance (Blog)]