Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.0
-
Fix Version/s: 2.1.2
-
Component/s: Engine - Reference and data management
-
Labels:None
Description
Deletion of data at shutdown seems to be very inefficient. It takes a surprisingly long time.
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Except for constant re-construction of ProvenanceAccess and it's spring/database connections (which was fixed), the other most inefficient finding was that Reference Manager deletion done by the DAO objects are done using a select and then a hibernate deleteAll. Attempted to change this to a more SQL-like DELETE FROM statement, which was more efficient, but which failed with db integrity exceptions on Lists due to Hibernate not cascading the delete correctly to also delete the ListContents.