EclipseLink/Development/Performance
From Eclipsepedia
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
| Component | Test | Description |
| Core | PerformanceComparisonModel | Compares the performance of different operations (reading vs batch reading) |
| Core | PerformanceTestModel | Compares performance for each test against previous result. |
| Core | ConcurrencyComparisonTestModel | Compares concurrency for each test using 1 to 32 threads. |
| Core | ConcurrencyRegressionTestModel | Compares concurrnecy for each test against previous result. |
| JPA | JPAPerformanceRegressionModel | Compares performance for each test against previous result. |
| JPA | JPAConcurrencyComparisonTestModel | Compares concurrency for each test using 1 to 32 threads. |
| JPA | JPAIsolatedPerformanceRegressionModel | Compares performance without caching. |
| JPA | HibernateJPAPerformanceRegressionModel | Compares EclipseLink with Hibernate. |
| JPA | OpenJPAJPAPerformanceRegressionModel | Compares EclipseLink with OpenJPA. |
| JPA | EssentialsJPAPerformanceRegressionModel | Compares EclipseLink with TopLink Essentials. |
| JPA | TopLinkJPAPerformanceRegressionModel | Compares EclipseLink with TopLink. |
| JPA | JPAMemoryLeakModel | Tests for possible memory leaks in EclipseLink. |
Results
- Results comparing EclipseLink 1.0 with TopLink® Essentials
- Results comparing EclipseLink 1.1 with EclipseLink 1.0
- Results comparing EclipseLink 1.2 with EclipseLink 1.1

