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/Performance"

m (Links)
m (Links)
Line 44: Line 44:
 
* [http://java-persistence-performance.blogspot.com/ Java Persistence Performance (Blog)]
 
* [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://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#Performance Performance characteristics for 1-512 parallel threads for a single 8-core i7-920 as part of a distributed JPA application]
+
* [http://wiki.eclipse.org/EclipseLink/Examples/Distributed#Performance 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:50, 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

Back to the top