How do I deal with project bloat? Long Save time is getting worse?

Question

Here are the FB posts I have got about this issue. I tried to paste them neatly but didn't work.
To be honest I am baffled that such an advanced NLE has so many issues. There should be a warning about the Warp Stabilizer messing up a project I had no idea till now.
This was my question to a PP user group on FB.
I am cutting a 60+ minute doc with lots of source material and the project takes a dogs age to save now which is beginning to interrupt my workflow. I would have thought the save would take less time depending on how much work was done since the last save. I suppose working with Proxies might be the solution but I am already 70% done.
Here are the responses
Saving the project file on an SSD might be a good idea.
Your project size is slowing you down. Create a couple of projects, each containing a part of the footage. Organized in bins as needed. Call them footage projects. Create an other project named edit and cut in there. Use the media browser to browse the footage projects. Import what you need and use search bins to keep it organized.
If you didn't transcode your footage before you started the project it could be part of the problem. And like the other post says only having the footage you are currently working on will also help. The claim that you don't have to transcode when working in Premiere is misleading because in most cases when working with many different source codecs transcoding will always improve your computers performance.
I had the exact same experience cutting a 90 min feature with 120 hours of Pro Res 4444 footage. Long save times are caused by project bloat, either by having too many assets loaded or a lot of warp stabilizer effects applied. Transcoding will only affect playback performance and exports - it doesn't sound like it's the problem in this case.
only some codecs (4K GoPro, 6K R3D, lengthy h264/AVCHD clips for example) benefit from transcoding and will be snappier and playback smoother. But transcoding will never ever help the loading or saving time of your project
Don't apply warp stabilizsr to everything. All those coordinates get stored in project file
All I can say is that I worked on a Premiere project in November where my computer spent up to 5-7 minutes scanning through all the different directories with footage after the project was open before I could play back the sequences in my project. I ha...
some of the ftg is in need of stabilization so I did use the warp stabilizer but not excessively. 15 x 3-10 second clips. Is there a way of managing the storage of the coordinates too minimize the hit on the project size?
nope. Try importing existing project into a new project.
I usually stabilize footage in a separate project to avoid huge project files, and export the stabilized result. Then I use the stabilized version in the main project.
I also work with Nested Sequences a lot. Working in short, manageable timelines. When opening a large project, Premiere will find the footage for the active sequence first, so I can start working quickly, while Premiere is still finding the rest of the footage.
Could do your warp stabilizing in AE and export renders of them, then import those renders into your project so the are just media files instead of files with stabilizer tracking points.

Answer 1

I usually stabilize footage in a separate project to avoid huge project files, and export the stabilized result. Then I use the stabilized version in the main project.
That would be something like  the advice I would have given
and  more likely...
Save heavy duty  FX application until after you have locked down your edit. (eg Blurs , Warp, 3rd party FX(MB)
I Create separate sequences or Duplicate Projects for many reasons.  eg CC/Grade  and
Warp Stabiliser ...definitely.  Its even has a slow save  impact on After Effects Projects!