[Matthew Woods] “From what I have read, CPU clock speed is important, but AE can’t make use of multiple processor cores anymore, so fewer cores with a faster clock speed are better.”
Though this is the prevailing wisdom online, the truth is more complicated than that. Some things in Ae use multiple cores very well, some things use multiple cores very poorly, and more and more is moving onto the GPU.
With Ae CC 2014 and earlier, more RAM helped with “multiprocessing” — a feature that silently launched multiple copies of the Ae renderer in the background to work on multiple frames at the same time. Each copy of the renderer required its own space in RAM (with its own separate layer caches), so lots of RAM was required. Starting with Ae CC 2015, Adobe has been trying to modernize Ae’s internals without completely blowing up compatibility or UX. This was a step back in some regards, but a step forward in others and hopefully a good base for continued improvements.
We use Render Garden from Mekajiki a lot to emulate that old workflow with the current release of Ae (and with all the high RAM requirements it implies):
https://www.mekajiki.com/rendergarden/
With vanilla Ae today, RAM is mostly used by the cache, so your RAM usage will be driven by a combination of factors: the size of your raster, the bit depth you’re working in, the number of layers in your comp, and the duration of your comp.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn]