Jump to: navigation, search

Difference between revisions of "EclipseLink/Performance"

(Features)
m (Links)
(5 intermediate revisions by 2 users not shown)
Line 14: Line 14:
 
** Fetch groups (query, default, dynamic)
 
** Fetch groups (query, default, dynamic)
 
** [[Using_EclipseLink_JPA_Extensions_(ELUG)#Fetch_Size|Fetch size]]
 
** [[Using_EclipseLink_JPA_Extensions_(ELUG)#Fetch_Size|Fetch size]]
** Pagination (firstResult, maxResult, ROWNUM filtering)
+
** [[EclipseLink/Examples/JPA/Pagination|Pagination]] (firstResult, maxResult, ROWNUM filtering)
 
** Cursors (stream and scrollable)
 
** Cursors (stream and scrollable)
 
** [[Using_EclipseLink_JPA_Extensions_(ELUG)#Cache_Usage|Cache usage]] (in-memory, primary key)
 
** [[Using_EclipseLink_JPA_Extensions_(ELUG)#Cache_Usage|Cache usage]] (in-memory, primary key)
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]
 +
* [http://wiki.eclipse.org/EclipseLink/Examples/Distributed#Multicore_Analysis Performance characteristics for 1-512 parallel threads on a single 8-core i7-920 node as part of a distributed JPA application]
 
[[Category:EclipseLink|Performance]]
 
[[Category:EclipseLink|Performance]]

Revision as of 16:51, 24 March 2011

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

Features

EclipseLink's performance features include:

Benchmarks

Forum Posts

Links