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.
Difference between revisions of "EclipseLink/Performance"
(→Features) |
(→Links) |
||
| Line 42: | Line 42: | ||
* [[Optimizing_the_EclipseLink_Application_(ELUG)| EclipseLink User Guide - Optimization]] | * [[Optimizing_the_EclipseLink_Application_(ELUG)| EclipseLink User Guide - Optimization]] | ||
* [[EclipseLink/Development/Performance | Performance Development]] | * [[EclipseLink/Development/Performance | Performance Development]] | ||
| + | * [http://java-persistence-performance.blogspot.com/ Java Persistence Performance (Blog)] | ||
| + | * [http://java-persistence-performance.blogspot.com/2010/08/batch-fetching-optimizing-object-graph.html Batch fetching - optimizing object graph loading] | ||
[[Category:EclipseLink|Performance]] | [[Category:EclipseLink|Performance]] | ||
Revision as of 11:21, 10 November 2010
EclipseLink is dedicated to being the best performing, and most scalable JPA implementation.
Contents
Features
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