Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Performance"
(New page: EclipseLink is dedicated to being the best performance, and most scalable JPA implementation. ==Features== EclipseLink's performance features include: * Object cache ** Cache invalidation...) |
(→Features) |
||
Line 27: | Line 27: | ||
** Statement caching | ** Statement caching | ||
** Batch writing (JDBC, parametrized, native) | ** Batch writing (JDBC, parametrized, native) | ||
+ | |||
+ | ==Links== | ||
+ | * [[Optimizing_the_EclipseLink_Application_(ELUG)| EclipseLink User Guide - Optimization]] | ||
+ | * [[EclipseLink/Development/Performance | Performance Development]] | ||
[[Category:EclipseLink]] | [[Category:EclipseLink]] |
Revision as of 16:32, 24 March 2009
EclipseLink is dedicated to being the best performance, and most scalable JPA implementation.
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
- 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
- Weaving enhancements
- Transactions
- Attribute level change tracking
- Field level updates
- Database
- Connection pooling
- Statement caching
- Batch writing (JDBC, parametrized, native)