Context
Currently all the loadAll... methods in ExperimentDAOImpl are loading all records to entity classes without checking the size of records in the DB. In prod this might create an OOM if the DB records are huge in number.
Batch wise processing is required for the features which are relying in these calls.
Scrollable results Can help in achieving this, by fetching a fixed size of records till we complete the whole table, but the consumer features should also support batch processing and not one time processing as this needs to consistently communicate with DB
Context
Currently all the
loadAll...methods inExperimentDAOImplare loading all records to entity classes without checking the size of records in the DB. In prod this might create an OOM if the DB records are huge in number.Batch wise processing is required for the features which are relying in these calls.
Scrollable results Can help in achieving this, by fetching a fixed size of records till we complete the whole table, but the consumer features should also support batch processing and not one time processing as this needs to consistently communicate with DB