Large project, tragic performance

Question

I've been dealing with terrible performance - I thought the issue was ppro 25 (https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-25-performance-vs-24/m-p/15408676#M565829)

but yesterday I used 25 to work on a much smaller project and it was fine. Why would a large project kill performance? How can the volume of source media slow it down? Does it make a difference that the source media is from multiple paths? Does lots of warp stabilise data affect perfomace? Knowing this stuff would help develop best practice with large projects (and tell me when to start from scratch)
I'm going to to import this project into a new one today and see if that helps.

getho · Accepted Answer

I actually wonder if there's something going on with my graphics card. Yesterday it was absolutely choking. Just because why not I soft reset the graphics card driver, and performance improved a lot.

It would be good to know which bits of the project stay in ram - I've probably got a lot of room to optimise things (like storing stock clips on the same sequence - quick to use but they realy could all go into another sequence)

R Neil Haugen · Answer

You should try using the Productions mode, which breaks the entire "project" into sections of project files in a spiffy, organized manner ... and makes larger products much more efficient to do. It's what is recommended for all long-form, episodic, and large projects.

I went to it for my small shop, as it means that all my b-roll, sound libraries, and template sequences are available for use on anything I do. Slick.

And even if you don't their documentation has the best practical advice for using Premiere they've ever published ... largely because noted user Jarle Leirpoll wrote most of it.

Premiere Pro Productions Introduction

Using Productions in Premiere Pro

Adobe Long-form and Episodic Best Practices Guide

Jarle’s blog expansion of the pdf Multicam section: Premiere Pro Multicam