Difference between revisions of "EclipseLink/Development/Performance"

From Eclipsepedia

Jump to: navigation, search
(Results)
(Results)
Line 31: Line 31:
 
* [[/Results/1.1/|Results comparing EclipseLink 1.1 with EclipseLink 1.0]]
 
* [[/Results/1.1/|Results comparing EclipseLink 1.1 with EclipseLink 1.0]]
 
* [[/Results/1.2/|Results comparing EclipseLink 1.2 with EclipseLink 1.1]]
 
* [[/Results/1.2/|Results comparing EclipseLink 1.2 with EclipseLink 1.1]]
 +
* [[/Results/2.0/|Results comparing EclipseLink 2.0 with EclipseLink 1.2]]
  
 
===Links===
 
===Links===

Revision as of 15:42, 14 December 2009

Contents

Performance

This is the main development page for EclipseLink performance.

EclipseLink performance is tracked through several mechanisms.

  • Weekly regression performance unit tests.
  • Milestone third party product performance unit tests comparisons.
  • 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.

Results

Links