RAM maxing out after relinking

Thank you so much, @Pyromk1! Moving to the "Discussions" forum while we await any further troubleshooting.

Kevin

What happens if the media is living on internal drives, @Pyromk1? Better behavior or no change?

Thanks,
Kevin

Thank-you @R Neil Haugen  for such an in-depth reply.
I am reminded of how much of B h.264 is for decoding every time I use thumbnail view! We uses mainly Sony Alpha cameras for our work which have very few codec options. I also made the decicion that in terms of workflow I'd same time and storage building a machine that is capable of working with long-GOP clips rather than transcoding.
It has perfomred admirably until now and I'm struggling to understand why.

@Kevin-Monahan Thanks for your feedback. I'm actually using a Direct Attached Storage with a 10gb connection rather than Network Attached Storage. So the footage is already "local".
I've always transcoded to proxies when ive needed to from within Premiere. But as I can't open the project in premiere that wont be possible. Can you point me towards any articles detailing a workflow for this from (i'm assuming) media encoder. Then how do I get permiere to perform the final renders from my originals ?

In the meantime I've got a 128GB RAM kit on it's way to see if that is enough RAM for premiere.  

The fun part is that your media is resource-intensive to work with. Eight hundred long-GOP clips is a load ... as to simply show the next frame, the computer has to decompress up to 100 or more frames, and store them in RAM/cache files.

Now try and play that on a timeline, yea, it's a load. Your system has a decent 10-core CPU with QuickSync, so it's better at this than many. But still ... that is a ton of long-GOP media to work with.

I work for/with/teach pro colorists, most work on 'heavy iron' that makes my 24 core 128GB of RAM system look positively anemic.

And none  of the many colorists I know would ever grade a program of several hundred long-GOP clips without at least proxies ... most would simply t-code to ProRes before conforming the project into Resolve or Baselight. That's how poorly they view working with long-GOP files.

Even a few in a project, they will normally t-code to a workable intraframe codec.

We all wish it were otherwise, as long-GOP is so fast for the camera maker's to get encoding to small file sizes in camera. My Ursa Mini Pro 4.6k, even doing it's most compressed BRAW, still fills cards quite rapidly. Incredible media quality, but file size is not ... small.

It's one of those many trade-offs of Life. Maybe @RjL190365 could have some advice, as they know this hardware stuff so major. There might be something in your setup that could be tweaked.