Database sluggish

I've noticed that saving and retrieving as well as inserting new clips is getting sluggish in a project which is about 75 minutes long. Is there anyway to optimise the database to speed things up?

Hi Thom

How big/full is your database?

I seem to remember Resolve works faster from a smaller DB.

I have a few, but mainly split between 2 - Current Projects and Completed Projects
this way its never too full.

Hector

No idea.. DR doesnt supply any maintenance module as far as I can see?

Hector

No idea.. DR doesnt supply any maintenance module as far as I can see?

I meant "how big" as in, how many projects...

you can create numerous DBs and move projects between them.

aha.. only the one Big project so far

just dragging a WAV file from the media pool takes time, not to mention dragging it into the timeline. Once it crashed DR completely !

I suspect that the database needs optimising to speed up inserts and reads

aha.. only the one Big project so far

Is your DB on a fast drive?

Yes .. an internal SSD

The data is on an external USB3 Raid unit which is consistently fast

[Peter Chamberlain]

Can you backup your database and try the new 14.1.1 version which was just released?

[Peter Chamberlain]

Also, are you using DiskDB or Postgres?
What happens if you start a new project?

Tried latest update still very slow.. almost to the point where DR hangs but if I wait long enough it come back to life.

would a screen video of whats happening help you?

Works fine if I drag from the preview window to the output window and select eg place on top. Its when I drag a clip from the preview to the timeline directly that it 'hangs'. video or audio, makes no difference

[Peter Chamberlain]

Lets start at the beginning by detailing your system etc.. please review this too.

viewtopic.php?f=21&t=54509

With all due respect...

If you cannot reproduce this issue then it is a local issue for which I have found a workaround as described in my previous post. Ergo I do not think this is to do with my particular setup but more likely how the code manages the dragging and dropping of clips from the media pool.

Having worked with databases for nigh on 25 years (Msoft SQL) I hope I know a thing or two about them and how they work and the symptoms they exhibit when they don't.

I recently encountered some logistical/organizational issues with my own project database (encompassing more than 5 years' worth of projects, hundreds of them), and I went ahead and did this:

1) I sorted them all by Creation Date

2) I embedded the creation date into the Project Title

3) I created new year-specific external disk databases arranged as "2014_projects", "2015_projects", "2016_projects", and so on.

4) then I highlighted multiple projects from the same year, copied them to the clipboard, and pasted them over to the database. The copies now had new creation dates, but I knew their original dates because they were embedded in the Project Name (like Client_Title_10-2014).

5) once I verified the copies were good, I deleted the originals from the current project list. Now, I have a much, much smaller list of only this year's projects. Once January hits, I'll start 2018_projects and life goes on.

For the record (no pun intended), I think the database setup in Resolve 14 is much faster than 12. I think it takes some getting used to, but once you get how it works, it's actually pretty slick. Plus, you can backup those individual databases very easily. Have not crossed over to Postgres yet, but I may eventually do so.