Compare with

Comparison of DataNucleus with Derby embedded vs Hibernate with PostgreSQL server

Each of the following tables focuses on a specific database operation, where the last table presents average results comparison.

Speed comparison of JPA database persistence operations (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
Basic Person Test4.67.12.83.43.75.2
Element Collection Test2.42.91.61.72.02.3
Inheritance Test4.67.02.73.63.75.3
Indexing Test7.69.34.86.16.27.7
Graph (Binary Tree) Test1.63.01.42.91.52.9
Multithreading Test8.631.73.313.95.922.8
All Tests4.910.22.85.33.87.7

The results above show that in general Hibernate with PostgreSQL server is more efficient than DataNucleus with Derby embedded in persisting JPA entity objects to the database. Comparing the normalized speed of DataNucleus with Derby embedded database (3.8) to the normalized speed of Hibernate with PostgreSQL database server (7.7) reveals that in these tests, Hibernate with PostgreSQL server is 2.0 times faster than DataNucleus with Derby embedded.

A large performance gap has been detected when using multithreading with large transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (3.3) to the normalized speed of Hibernate with PostgreSQL database server (13.9) reveals that in that case, Hibernate with PostgreSQL server is 4.2 times faster than DataNucleus with Derby embedded.

Speed comparison of JPA database retrieval operations (normalized score, higher is better)

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
Basic Person Test6.85.514.911.510.98.5
Element Collection Test5.40.0257.60.0176.50.021
Inheritance Test8.85.214.814.011.89.6
Indexing Test9.24.614.113.311.68.9
Graph (Binary Tree) Test9.90.6115.80.7812.90.70
Multithreading Test11.911.311.517.011.714.2
All Tests8.74.513.19.410.97.0

The results above show that in general DataNucleus with Derby embedded is more efficient than Hibernate with PostgreSQL server in retrieving JPA entity objects from the database.

A huge performance gap has been detected when using JPA element collections with large retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.017) to the normalized speed of DataNucleus with Derby embedded database (7.6) reveals that in that case, DataNucleus with Derby embedded is 447 times faster than Hibernate with PostgreSQL server.

Speed comparison of JPA database query operations (normalized score, higher is better)

Retrieval Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
Basic Person Test39.155.57.56.123.330.8
Element Collection Test46.011.06.70.01626.35.5
Inheritance Test7.752.33.88.75.730.5
Indexing Test0.0530.0508.08.84.04.4
Multithreading Testfailed55.2failed9.2failed32.2
All Tests23.234.86.56.614.820.7

DataNucleus with Derby embedded has failed in 2 tests (see exceptions).

The results above show that in general Hibernate with PostgreSQL server is more efficient than DataNucleus with Derby embedded in executing the tested JPA queries.

A large performance gap has been detected when using class inheritance in the object model with small retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (7.7) to the normalized speed of Hibernate with PostgreSQL database server (52.3) reveals that in that case, Hibernate with PostgreSQL server is 6.8 times faster than DataNucleus with Derby embedded.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.016) to the normalized speed of DataNucleus with Derby embedded database (6.7) reveals that in that case, Hibernate with PostgreSQL server is 419 times slower than DataNucleus with Derby embedded.

Speed comparison of JPA database update operations (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
Basic Person Test4.05.33.82.73.94.0
Element Collection Test3.70.0674.50.0264.10.046
Inheritance Test4.45.44.83.84.64.6
Indexing Test5.25.44.24.34.74.8
Graph (Binary Tree) Test2.71.11.50.582.10.82
Multithreading Testfailed29.6failed6.3failed18.0
All Tests4.07.83.72.93.95.4

DataNucleus with Derby embedded has failed in 2 tests (see exceptions).

The results above show that in general Hibernate with PostgreSQL server is more efficient than DataNucleus with Derby embedded in updating JPA entity objects in the database.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.026) to the normalized speed of DataNucleus with Derby embedded database (4.5) reveals that in that case, Hibernate with PostgreSQL server is 173 times slower than DataNucleus with Derby embedded.

Speed comparison of JPA database removal operations (normalized score, higher is better)

Transaction Size =>Few EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
Basic Person Test3.55.31.34.22.44.8
Element Collection Test1.90.0201.6stopped1.70.0098
Inheritance Test2.45.11.34.21.94.6
Indexing Test6.69.51.96.34.37.9
Graph (Binary Tree) Test0.810.0120.930.0120.870.012
Multithreading Testfailed23.3failed21.8failed22.5
All Tests3.07.21.46.12.26.6

DataNucleus with Derby embedded has failed in 2 tests (see exceptions).

The results above show that in general Hibernate with PostgreSQL server is more efficient than DataNucleus with Derby embedded in deleting JPA entity objects from the database. Comparing the normalized speed of DataNucleus with Derby embedded database (2.2) to the normalized speed of Hibernate with PostgreSQL database server (6.6) reveals that in these tests, Hibernate with PostgreSQL server is 3.0 times faster than DataNucleus with Derby embedded.

A large performance gap has been detected when using database indexes with large transaction size. Comparing the normalized speed of DataNucleus with Derby embedded database (1.9) to the normalized speed of Hibernate with PostgreSQL database server (6.3) reveals that in that case, Hibernate with PostgreSQL server is 3.3 times faster than DataNucleus with Derby embedded.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with small transaction size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.020) to the normalized speed of DataNucleus with Derby embedded database (1.9) reveals that in that case, Hibernate with PostgreSQL server is 95.0 times slower than DataNucleus with Derby embedded.

Comparison of JPA/Database speed - the averages (normalized score, higher is better)

Transaction/Retrieval SizeFew EntitiesMany EntitiesAverage Score
 DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
DataNucleus
Derby embedded
Hibernate
PostgreSQL server
Basic Person Test11.615.76.15.68.810.7
Element Collection Test11.92.84.40.358.11.6
Inheritance Test5.615.05.56.95.510.9
Indexing Test5.75.86.67.86.26.8
Graph (Binary Tree) Test3.71.24.91.14.31.1
Multithreading Test10.330.27.413.68.821.9
All Tests8.012.15.76.06.99.1

The results above show that in general Hibernate with PostgreSQL server is more efficient than DataNucleus with Derby embedded in performing JPA database operations.

A large performance gap has been detected when using multithreading with small transaction/retrieval size. Comparing the normalized speed of DataNucleus with Derby embedded database (10.3) to the normalized speed of Hibernate with PostgreSQL database server (30.2) reveals that in that case, Hibernate with PostgreSQL server is 2.9 times faster than DataNucleus with Derby embedded.

On the other hand, Hibernate with PostgreSQL server is slower, for instance, when using JPA element collections with large transaction/retrieval size. Comparing the normalized speed of Hibernate with PostgreSQL database server (0.35) to the normalized speed of DataNucleus with Derby embedded database (4.4) reveals that in that case, Hibernate with PostgreSQL server is 12.6 times slower than DataNucleus with Derby embedded.

Other Head to Head DBMS/JPA Comparisons