Over time many customer CuratorDBs are likely to grow to a point where normal queries take far longer than expected. This is likely to be because of the sheer number of rows in the database, causing MySQL to take longer in identifying relevant rows for deletion. This is no more so relevant than on the Blobs table. 

Following major investigations, it's been found that database indexing expecially on the Blobs table can drastically improve performance. Therefore, as an initial step running the below query against a slow performing CuratorDB can be beneficial:

ALTER TABLE metadatablobvalues
ADD INDEX IDX_metadatablobvalues_asset_id (asset_id);

*It is advised that the CuratorDB is inactive as possible at the time of running. This is because the table gets recreated.