1. Beatrix Willius
  2. Valentina Database ADK
  3. Среда, Июль 03 2024, 12:07 PM
  4.  Подписаться через email
A user with a fast SSD says that his 250 GB database takes 2 hours to diagnose. The diagnosis is done with EVVerboseLevel.kNone and with the API not SQL. Usually, such large databases have lots of blobs.

Is it normal that the diagnosis takes so long?
Комментарий
There are no comments made yet.
Ivan Smahin Ответ принят
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.
Комментарий
There are no comments made yet.
Beatrix Willius Ответ принят
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.
Комментарий
There are no comments made yet.
Ivan Smahin Ответ принят
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.
Комментарий
There are no comments made yet.
Beatrix Willius Ответ принят
Okay, will do that and report back.
Комментарий
There are no comments made yet.
  • Страница :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.

Categories

Announcements & News
  1. 0 subcategories
Valentina Studio
  1. 2 subcategories
Valentina Server
  1. 4 subcategories
Valentina Database ADK
  1. 0 subcategories
Valentina Reports ADK
  1. 0 subcategories
Other Discussions
  1. 2 subcategories
BETA Testing
  1. 0 subcategories
Education & Research
  1. 0 subcategories