Resolve hammering HDD

In between working on a project last night and loading it again this morning, resolve has started absolutey hammering my HDD. I purposefully move all timeline media to my m.2 nvme drive before adding it to the timeline/mediapool and resolve is installed on the m.2 drive also. There should be no reason for it to be accessing the HDD, let alone hammering it so hard I can't do anything on my rig for long periods of time. I suspected it might be caching on their, so made loads of room on the m.2 drive, cleared the render cache then generated optimised media for the timeline, but it's not done a lot to improve the situation.

Any help on this would be greatly appreciated before I throw my rig out the window and jump after it.

This is on v17.0

Resolved with an upgrade of ram capacity. Still unknown why it went from working fine one evening to caching on the HDD and freezing the rig up for hours at a time the next day.

Where is the project set to save the Cache/Proxy/Optimized Media?

Check your Preferences>System>Media Storage to make sure the HD isn't listed.

Where is the project set to save the Cache/Proxy/Optimized Media?

Check your Preferences>System>Media Storage to make sure the HD isn't listed.

Yeh everything is set to save to the m.2 drive. It's a Seagate firecuda 520 so nice and rapid for any caching that would be needed and I made room for it. Checked and all the optimised media etc was being saved on that drive in c:/voii or whatever it is and had taken a far chunk of space already, but for whatever reason just decided to anihilate the HDD for on the fly caching. Maybe a Windows setting causing it?

What files are being written to the HD?

My guess is that before upgrading your RAM you were running out and hitting the disk for swap, which is not fast.

What files are being written to the HD?

Can't find a dam thing. Do anything else on the pc and it's fine. Load my project and all I get is the crunch crunch crunch of the HDD being slammed, both read and write, but can't find any footprint of resolve.

My guess is that before upgrading your RAM you were running out and hitting the disk for swap, which is not fast.

yeh definitely running out of ram, but there is no reason it should have been touching the HDD. Wasn't the day before.

yeh definitely running out of ram, but there is no reason it should have been touching the HDD. Wasn't the day before.

I'm sure it would have been Windows accessing the hard drive because Resolve was asking for more RAM than was available. Virtual memory.

Can't find a dam thing.

Use Resource Monitor. Sort the Disk activity by Total.

Can't find a dam thing.

Use Resource Monitor. Sort the Disk activity by Total.

I can see the HDD being used by resolve in resource monitor, but there isn't any files or folders being generated on on the HDD that I can find. There were only 2 folders on it so it should have been blatantly obvious.

yeh definitely running out of ram, but there is no reason it should have been touching the HDD. Wasn't the day before.

I'm sure it would have been Windows accessing the hard drive because Resolve was asking for more RAM than was available. Virtual memory.

But the question is why it's using the HDD all of a sudden and not the m.2 drive. It wasn't just 9 hours before or the 3or4 days prior.

I can see the HDD being used by resolve in resource monitor,

OK. Is it reading, or writing?

I can see the HDD being used by resolve in resource monitor,

OK. Is it reading, or writing?

Was both. Would switch between both to just read, to just write.

OK. In the Disk section of Resource Monitor, it will show you what files are being read/written.