Hi Beatrix,

I would recommend cloning the db. It could be much faster after that. If the problem reoccurs - probably BLOB's segment size should be changed.

I forgot to add: the user wasn't able to finish running a diagnosis. I recommended a clone so that the 2 hours are after doing a clone.

Do you mean the db has been cloned already to solve the "slow diagnose issue"?
And that cloning does not help?

Ok, there are a few ways to find the reason of that slowness:

- Check the diagnose log - errors, enormous blobs' segments (in the assumption that the reason for slowness is BLOB's segments count);
- Try to to diagnose "manually" - for each table in the db (or even each field) - it should help to find the source of that slowness.

Okay, will do that and report back.