another thing you can do as you try your own benchmarks with various settings, is to run the activity monitor (applications>utilities>activity monitor).
that app will let you see the various processes that are running on you mac. when you render with multiprocessing on, you’ll see some processes called aeselflink. these are the render engines that ae uses when multiprocessing is enabled (one for each core that is set in the multiprocessing prefs).
the values you are interested in are the cpu values. when you see values that are around 100, that means that the process is using about all the resources of a single cpu. you can see values higher than 100 if extra cores are available to help rendering — so you have 4 cores, but tell ae to use 2… there are 2 available to help rendering when ae is rendering something that is multi-threaded. note that not all effects are multi-threaded, but many are.
if you see values that are much lower than 100, then you are having a data bottleneck somewhere. usually, it’s with the ram. with faster and greater numbers of cpus, computers have a greater ability to go through data quickly. by having more ram available, you can help assure that the cpus are running at there full potential and not waiting around for data to process (aka, starving). in a case like that, decreasing the number of cpus increases the amount of ram available and can increase performance.
and, as todd’s blog points out, your system has other processes running in the background that need ram to keep things running smooth. so if you tell ae to use all your resources, that can affect performance negatively too.
as far as the drives causing a bottleneck, with 2-4 cores, i don’t think that will be a problem often. but with fairly effect light comps with high data rate footage files, you could see a bottleneck. it’s easy to demonstrate this, just add 10 hd clips to a comp, all overlapping and set their opacities to 10%, then render (or ram preview). if you look in the activity monitor, you’ll probably see that the cpu usage for the aeselflinks is fairly low. this is due to the amount of data that has to travel from the drives, to the ram, then to the cpus… and the cpus are not having to do much processing so they are spitting out frames faster than they can get the data from the drives.
that scenario is not a very common one, so i don’t think you’ll see that too often. but, perhaps if you did a lot of color correction for uncompressed hd footage, you may be able to speed the process up by having a faster drive option… the imac *may* have an extra sata2 drive bay inside, by getting a fast internal sata2 drive, you *may* be able to improve performance (in a case like this).
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW