Skip to main content
Known Participant
April 10, 2012
Answered

Which "Optimize Memory For" setting is best ?

  • April 10, 2012
  • 5 replies
  • 97000 views

I don't understand this..Or I think I've used it wrong..please help?

By default, Premiere Pro renders video using the maximum number of available processors, up to 16. However, some sequences, such as those containing high-resolution source video or still images, require large amounts of memory for the simultaneous rendering of multiple frames. These sequences can force Premiere Pro to cancel rendering and to give a Low Memory Warning alert. In these cases, you can maximize the available memory by changing the rendering optimization preference from Performance to Memory. Change this preference back to Performance when rendering no longer requires memory optimization.

  1. Select Edit > Preferences, and select Memory in the Preferences dialog box.
  2. In the drop-down list next to Optimize Rendering For, select Memory.
  3. Click OK, close Premiere Pro, and reopen the project for the new preference to take effect.

Does setting to MEMORY only benefit lower end systems with bottlenecks, or do you use this settting on higher end machines too?

I've always had mine set to MEMORY because I thought it would make better use of the memory. Now I have a higher end machine with 16GB of ram. And I just read a thread where someone said set it to peroformance if you want to see more CPU/RAM utilization..so now I'm confused.... Do I set it to PERFORMANCE or MEMORY w/ 16GB of ram (core i7 2600k @ 4.2ghz)? Also if you could explain why. Thanks!

    This topic has been closed for replies.
    Correct answer Todd_Kopriva

    Only switch to Memory to get past instances that give the error message mentioned in the documentation.

    5 replies

    WellMarks
    Participant
    April 28, 2023

    I still dont get it. I have 32gb ram, a 3080 12gb and an ryzen 7 2700x, which one should i use? Performance or memory? With this config i still have problems to render 4k compositons. Can someone help?

    Peru Bob
    Community Expert
    Community Expert
    April 28, 2023

    Use Performance unless Memory allows better performance.

    What are the hard drives (how many, what kind, what is on each, what capacity, and how full)?

    WellMarks
    Participant
    April 29, 2023

    i have one ssd nmve 512gb and one ssd 480gb ( i will upgrade this year) 
    So, if i put all my archives on the Nvme, the render would be more smooth, right?

    Participant
    October 9, 2022

    Hello
    My system has specifications

    Core i7 10700 comet lake
    64 GB installed RAM

    In your opinion, which option is suitable for smooth working environment of Premier pro???
    Please provide the correct answer
    thank you

    January 5, 2020

    I tried this very procedure but still the problem keep coming what should i do next am using 8gig memory one stick

    Ann Bens
    Community Expert
    Community Expert
    January 5, 2020

    Upgrade your ram.

    giannisa26306314
    Participant
    December 30, 2016

    oh ! you save me ! i was OC my pc all day (last day of year) to find why all these errors ! i used performance and now in memory the render is more faster and there is no errors at export ! thanks a lot !

    Todd_Kopriva
    Todd_KoprivaCorrect answer
    Inspiring
    April 10, 2012

    Only switch to Memory to get past instances that give the error message mentioned in the documentation.

    milkmadeAuthor
    Known Participant
    April 11, 2012

    Thanks for the reply Todd, much appreciated! I guess I was thinking too hard about it, makes sense~

    May 13, 2012

    Wow!!! this helped A LOT....i was getting some message some place when i think checking a box about render at max depth or some thing like this that suggested i use Memory as my setting...So, i did....then began my renders....and got these CRAZY render times of 50 or more hours.....Now, i changed back to Performance and i'm seeing about half that---i can't say i'm crazy about 24-25 hours render times....BUT, sure is better than 50+ hours rendering...

    None-the-less my ratio seems to always be falling at 27mins of encode/render time to 1min of video....still FAR TOO MUCH.