Please try recommended memory settings for After Effects CS5 and give feedback.

Oct 05, 2010 Oct 05, 2010

Copy link to clipboard

Copied

We just posted a new set of recommendations for memory settings for optimum performance for After Effects CS5, and we'd like to know how they're working for you.

Please read this blog post and then respond to this thread with your results:

"Please try recommended memory settings for After Effects CS5 and give feedback."

Views

43.7K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

System Spec's :  2.66Ghz 8-core (16 threads) Mac Pro 4,1 with 24GB RAM (4x2GB + 4x4GB)

Composition : 6400 x 720 pixels, lots of shape layers, feathering / blurring, Trapcode Particular, Fractal Noise.  NO source files or footage.

Only other application running was Firefox (light usage)

Results:

RAM for other apps
RAM per core
Cores used
Speed
4283.13
6273.20
6343.00
81145.16
81.593.11
826
2.53
8342.56
8424.04
10252.55

This pretty much confirms teh recommendations Todd posted.  In this case a VERY small speed increase was gained by allocating 1GB less per core, probably due to the comp having no source footage.  When I get time I'll run the same tests on a footage-heavy comp.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

Hi,

I ran some quick tests on an older project (one of the only I have without lens blur and therefore one of the only where mp is not disabled).

It's 720x540, no video, all animated still images. Some fairly hi-res (2-3K), others only a few hundred px. Several adjustment layers over the whole comp for overall texture effects that really slow the whole thing down a lot.

These are times it took to render one second of the project.

1:44 (recommended settings)

Screen shot 2010-10-06 at 12.08.48 PM.png

1:18

Screen shot 2010-10-06 at 12.12.41 PM.png

1:05

Screen shot 2010-10-06 at 12.15.46 PM.png

So in this case the recommended settings actually delivered the worst performance by far.

I was confused about one thing in the explaination, when you mentioned setting aside all that ram for other applications, to me it sounded a little like that 6GB of ram is actually available to the foreground process of AE but not the background processes. Is this the case or is it really totally unavailable to AE?

BTW this is a 8-core Mac Pro 2.8 ghz, 16 gb ram, OS 10.6.4

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

I've been playing with multiprocessor settings on a number of computers, and I'm always noticing the same problem: when I try settings that seem reasonable, "Actual CPUs that will be used" drops to zero.

For instance, right this very moment: I have 12gb of RAM, 3gb reserved for other applications and 2gb allocated for background CPUs. If I try upping the allocation to 3, "Actual CPUs that will be used" now says 0. Which I presume means multiprocessing is actually disabled. Unless I'm misunderstanding what that means?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

> I have 12gb of RAM, 3gb reserved for other applications and 2gb allocated for background CPUs. If I try upping the allocation to 3, "Actual CPUs that will be used" now says 0. Which I presume means multiprocessing is actually disabled. Unless I'm misunderstanding what that means?

12GB - 3GB reserved for other applications leaves 9GB. Setting minimum allocation per background process to 3GB also sets the minimum allocation for the foreground process to 1.2*3GB=3.6GB. So, 9GB - 3.6GB = 5.4GB. That only leaves enough RAM for one background process at 3GB. Keep in mind that if the background processes are rendering, then the foreground process is not. There's no point in starting up only one background process; so, in this case no background processes are started. Hence, the result that you see.

If you were to allocate 2.7GB as the minimum per process, then there'd be enough RAM for two background processes.

Note that you can set the allocation to whatever you want; you don't have to just use the values in the menu. See my comment at the bottom of this page.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

Does that mean that the recommendation for 12gb is to not use multiprocessing?

I know "quick tests" in AE usually don't mean a thing, since each project renders differently, but I outputted a second from the project I'm working on -- some Liquify, lots of Particular, tons of precomps. With 3gb for other apps / 2gb per CPU (my go-to settings), I got a render time of 1:44. Rerendering the same frames with 4gb / 3gb, which disables multiprocessing, took 4:28.

So, I'm going to go out on a limb and say the 4gb / 3gb recommendation seems... off.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

Thanks, Aaron. For feedback to be valuable, we really need to know what kind of footage is being used and what the pixel dimensions are of footage and compositions. If you're working with smaller frames, then less memory per process is required.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

All layers are 1920 x 1080. 20 layers total, about half of those are PSD layers (all from the same PSD), the rest just solids. No footage.

Seven instances of Frischluft (Out Of Focus), one instance of RSMB, one instance of Optical Flares, one Liquify. Two instances of Particular that are really heavy -- 500 particles / sec with 1500 particules / sec aux system.

PSD layers were from an 8-bit file. Test render was a 16-bit TIFF sequence, 51 frames long.

Rendering on 3 cores (2gb / core) takes about 1/3 the time it takes to render with multiprocessing off (setting 3gb / core). Which is kind of what you'd expect.

Hopefully this helps.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Oct 13, 2010 Oct 13, 2010

Copy link to clipboard

Copied

This is very helpful Aaron. It could be that you get fine results with just 1.5GB/ bkgnd process. If you have time, please up the reserved memory to 4GB with the BG cpu set to 1.5GB and try that for a while. Let us know how that works both for performance and for a working, all day setting that doesn't get starve the OS when you have been working for hours with the app.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 07, 2010 Oct 07, 2010

Copy link to clipboard

Copied

Someone asked if the "Ram reserved for other applications" included the AE foreground process. It doesn't. It's possible the recommended settings in this thread are overly conservative, but it's been established that the settings we shipped with were too aggressive. The OS, especially OSX, needs quite a bit of memory headroom. Being too aggressive with this setting can result in swapping to disk unnecessarily which takes a very long time.

Aaron Hildebrandt:

I agree that the 12GB settings are not ideal. Splitting the difference between the 8 and 16GB settings would be better. Off the top of my head, I'd say your "goto" settings(3GB reserved, 2GB per core) sound good.

Dan Ramirez

After Effects

QA Engineer

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 13, 2010 Oct 13, 2010

Copy link to clipboard

Copied

Since AE is capable of sending crash reports to you guys, why not build in the ability to send the essential render information? Size of comp, no. of layers, no. + data size of source files, render settings, system specs and render time.  Make it optional and completely secure, confidential, anonymous etc etc

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

ok, just ran some test here with a small project that includes:
6 precomps of large images turned into 3d buildings, a couple of lights, couple of adjustment layers, camera with slow pans and moves, 1080p24 sized.

rendered to default best settings and lossless.

machine: early 2008 8-core 2.8GHz, 16GB matched ram, rendering to 3x750GB Raid 0.

numbers mean this:(ie: 4-2-4.mov, 4GB for other apps, 2GB per BG proc, 4 cores used.

MULTIPROCESSING OFF:
2min, 12sec

MULTIPROCESSING ON:
3-1-8.mov: 1min, 16sec
3-1.5-7.mov: 1min, 4sec
3-2-5.mov: 1min, 4sec
3-3-3.mov: 1min, 11sec

4-1-8.mov: 1min, 15sec
4-1.5-6.mov: 1min, 4sec
4-2-4.mov: 1min, 6sec
4-3-2.mov: 1min, 25sec

6-1-6.mov: 1min, 8sec
6-1.5-5.mov: 1min, 4sec
6-2-3.mov: 1min, 11sec
6-3-2.mov: 1min, 22sec

NUCLEO PRO 3:
1min, 37sec

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

Thanks for the feedback so far.


Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 06, 2010 Oct 06, 2010

Copy link to clipboard

Copied

On my 8 GB system, Win 7, I've been running 1.5GB reserved with 1.5 allocated per CPU. Uses 3 CPUs. If I reserve 2GB, I only get 2CPU which is waste on Quadcore.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 07, 2010 Oct 07, 2010

Copy link to clipboard

Copied

sv2studios:

I know our users want AE to use all of your cores, but try and think beyond "use all my cores" into "help me work as fast as possible". If you don't provide enough memory to your background processes, they'll be very inefficient and slower than if you used fewer cores. It's only "wasting a quadcore" when RAM AND CPU is available and unused.

Thanks for all the feedback. This is helpful to us.

Dan Ramirez

AE QA

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 07, 2010 Oct 07, 2010

Copy link to clipboard

Copied

Dan,

I understand your point, but I get much better render times on most stuff with 3 cores vs 2 - that was my wasting comment. At least under Win 7, I don't see issues with those settings unless AE is bumping up against frame buffer. But those I render on my Quad with 16GB which works much better.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 07, 2010 Oct 07, 2010

Copy link to clipboard

Copied

One note from our test set-up:

Our engineers do custom installs they had to check on drivers. long and short, be sure the CUDA driver is installed (properly).

That combined with the recommended settings ensures a real performance boost. Thanks for this Todd it was a mystery in CS4!

We're still working on combinations and continuing with plug-in testing which is where we see huge differences. We'll post what we find.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Oct 08, 2010 Oct 08, 2010

Copy link to clipboard

Copied

Thanks for all the good feedback. The results reported are similar to those we are seeing in-house.

After Effects is a deep product that gets exposed to many workflows, from web animation to IMAX film compositing. Because of this broad exposure, there is no one ideal setting for all
rendering. The proposed memory preference settings are just a starting point with the goal of a better out of the box experience when the user first turns on Render Multiple Frames Simultaneously multiprocessing. These settings are what the user would experience with a fresh set of preferences.

AE CS5’s current memory settings are the minimums necessary for Render Multiple Frames Simultaneously multiprocessing. We are thinking of raising the default preference settings to those listed on Todd’s blog (
http://bit.ly/ckIriV ) so that more users get satisfactory results without having to first tweak the memory and Render Multiple Frames Simultaneously multiprocessing settings. They are not meant to be a solution for every type of project. If one is working in NTSC resolution, lower settings might be acceptable. If one is working with RED footage in complex compositions, higher settings will be necessary for best performance.

RAM reserved for other applications:
By reserving more memory for other applications there is also more memory reserved for the operating system buffers. This is beneficial because it stops the OS from swapping to disk during memory intensive tasks. If you find that over time as you work with a project that interactions are slowing down and taking much longer than normal, it could be that the OS is swapping to disk. Look to see if the hard drive light is flashing almost constantly. On the Mac, open the Activity Monitor  window (in the Utilities folder) and click on the System Memory tab. If the free memory is very low and the Swap used is high (over 500MB) and rising with each frame rendered, the OS is swapping. To alleviate this condition, raise the reserve memory setting in After Effects, save the project and restart the app. On the Mac, it may also help to restart the OS.

RAM allocation per background CPU:
We are also proposing raising the default background CPU setting from .75GB/ background CPU to 1.5GB / background CPU. The testing for these settings was done with a baseline of 1.5GB/ background CPU for
Render Multiple Frames Simultaneously multiprocessing. This combination of reserving more memory on systems with generous amounts of RAM + higher background CPU memory allocations achieved successful, fast renders over a variety of real world HDV and HD projects.

Managing memory for
Render Multiple Frames Simultaneously multiprocessing is complex. Think of each background instance as a mini After Effects. There are definitely projects that are going to require more memory per background CPU than others. For example, if the project will not render well with Render Multiple Frames Simultaneously multiprocessing off on a 2GB machine, it’s not going to render well with 2GB allocated to the background processes either. If you find this is the case, raise the background CPU allocation to a level that achieves the best result. In general we have found that web and NTSC work usually can be done with 1GB/ background CPU. HDV and HD work will usually need from 1.5 to 2GB/background CPU. Higher resolution work may need 3 or even 4GB/background CPU.


Please keep trying these proposed default settings with your projects and let us know how they work for you. Most importantly we need to know if they help reduce application slowdowns due to memory swapping, over the course of a day's work. That is the primary goal for the new defaults.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 29, 2010 Oct 29, 2010

Copy link to clipboard

Copied

an Forgetaboutit.

Message was deleted by: craulmedia

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 09, 2010 Dec 09, 2010

Copy link to clipboard

Copied

(Sorry, I accidentally posted this as a reply the the blog post... reposted here for convienence)

Thanks for this update/page. I’ve been trying to wrap my head around this issue over the past few days as I’ve struggled exporting 6 SECONDS of 720 24p footage.

My first test was as follows:

8-core with 24GB of Ram
RAM reserved for other applications: 3
CPU’s reserved for other applications: 2
RAM allocation: 1 GB
AE says that the actual number of CPU’s used: 15

Render time for a (6 second, 720 24p Quicktime animation codec, RGB+, millions of colors +): 3 hours 6 min – granted there are a lot particles involved, but thats still an incredible amount of render time per frame.

So I dug around, changed a few settings in the composition (decreased the amount of particles from 4000 to 2000 and moved the camera a tad bit to the side) and I came up with this:

RAM Reserved for other applications: 3GB
CPU’s reserved for other applications: 1
RAM allocation per background CPU: 3GB
Actual CPU’s that will be used: 5

Render time: 16 min and 59 seconds!

Granted, it still is only 6 min of footage, but 17 min. is a hell of a lot better than before. I’ll do some more tweaking and see if I can better the Render time, but I guess I’ve discovered the power of leaving enough RAM for each CPU to use up.

Anywho, thanks for all the help you’ve put into this so far, I look forward to seeing what the AE team comes up with for performance boots in the next iteration.

-Dylan

I should also mention that I’m running 64-bit Win 7, and that I did not have “Use Open GL Render” checked (although would I/Should I see a performance boost with this box checked in the render settings?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Dec 09, 2010 Dec 09, 2010

Copy link to clipboard

Copied

> I should also mention that I’m running 64-bit Win 7, and that I did not  have “Use Open GL Render” checked (although would I/Should I see a  performance boost with this box checked in the render settings?

No. Don't use the OpenGL renderer for anything that you care about the appearance of. It is a preview renderer that speeds some things up at the expense of the appearance of the image. And it often causes other problems.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 04, 2011 Jan 04, 2011

Copy link to clipboard

Copied

Anyone else have this problem?

Regardless of how much I tell AE to "Leave for other applications," it never fails to use up every drop of RAM until I'm left with a stuttering desktop and 17MB +/- of RAM left. This happened before in CS4 but I used Nucleo to get around it (although that sometimes still gave me problems). Recently switched to a brand new MacPro 12 core with 26GB of RAM. I launch AE and open my file (still 19GB RAM free at this point) and hit render. Mid-way through it drops way down to __MB. Other times, I'll work for a while, hit render and walk away. Come back when the render should be finished and it is taking twice as long. At that point, I need to quit out and restart AE and do a new render, then it is back to normal. Not sure what's up as I never had any of these issues back in CS2 or before but once I went up to CS4/CS5 it has never worked right.

Similar problem is during RAM previews of larger files. Hit RAM preview and it takes forever "loading projects" in the background. I read that it supposed to only happen the first time you RAM preview but it happens to me every time until I render something. If I turn off Multiprocessing, that immediately goes away. When I view the Activity Monitor, the individual render engines "aeselflink" are all open during the "loading projects" vortex so I have no idea why it continues to do it.

The most recent settings when I had the problem listed above with 19GB RAM free before launching AE.

RAM reserved for other apps: 11GB

CPUs reserved for other apps: 4

RAM per CPU: 2GB

Actual CPUs used: 7

Of course sometimes this happens while I'm working in other apps, but sometimes the only things that are open are Mail and Safari. I mean, I'm working with 26GB of RAM here! Shouldn't AE recognize how much RAM is available at launch and leave the amount listed in the prefs?

Am I the only one experiencing this?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Jan 04, 2011 Jan 04, 2011

Copy link to clipboard

Copied

Sounds wrong for sure. Are there any 3d part effects involved? Please submit a screenshot and a sample project (without footage) that has this issue to : aebugs@adobe.com. We'll take a look and see what is happening.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 04, 2011 Jan 04, 2011

Copy link to clipboard

Copied

Some have AE 3D some do not. The problem here is that it doesn't just happen on one particular project, its been happening for years and on 2 different machines in both CS4 and CS5.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Jan 05, 2011 Jan 05, 2011

Copy link to clipboard

Copied

It could be that this is happening in multiple situations, but we need specifics. For example, CS4 multiprocessing is quite different than CS5. There are many vast improvements in CS5 not the least being that it is a 64bit application able to address a much larger memory space.

Having concrete specific examples is the best way to address this issue and to see if developing solutions are effective. Please submit a project or projects illustrating this issue. Also include a screenshot of the Memory and Multiprocessing preferences panel on the system.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines