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

EclipseLink/Development/Performance

< EclipseLink‎ | Development
Revision as of 09:23, 23 July 2014 by Martin.grebac.oracle.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This is the main development page for EclipseLink performance.

EclipseLink performance is tracked through several mechanisms.

  • Milestone concurrency regression unit tests.
  • Milestone performance regression unit tests.
  • Public standard benchmarks such as SPECjAppServer ®.

Tests

ComponentTestDescription
CorePerformanceComparisonModelCompares the performance of different operations (reading vs batch reading)
CorePerformanceTestModelCompares performance for each test against previous result.
CoreConcurrencyComparisonTestModelCompares concurrency for each test using 1 to 32 threads.
CoreConcurrencyRegressionTestModelCompares concurrnecy for each test against previous result.
JPAJPAPerformanceRegressionModelCompares performance for each test against previous result.
JPAJPAConcurrencyComparisonTestModelCompares concurrency for each test using 1 to 32 threads.
JPAJPAIsolatedPerformanceRegressionModelCompares performance without caching.
JPAHibernateJPAPerformanceRegressionModelCompares EclipseLink with Hibernate.
JPAOpenJPAJPAPerformanceRegressionModelCompares EclipseLink with OpenJPA.
JPAEssentialsJPAPerformanceRegressionModelCompares EclipseLink with TopLink Essentials.
JPATopLinkJPAPerformanceRegressionModelCompares EclipseLink with TopLink.
JPAJPAMemoryLeakModelTests for possible memory leaks in EclipseLink.

Links

Back to the top