Mailing List ? Message #44404
From: Steve Forde <>
Subject: Re: [AE] (OT) An example of a PC version of a Mac Pro with today's tech for AE
Date: Tue, 12 Jun 2012 14:53:46 -0700
To: After Effects Mail List <>
Just for clarity - I think a minor (perhaps major!) point got lost.

HT is very powerful for AE on a normal basis. †Many effects, processes etc can utilize the benefits of spawning many threads and having the additional semi-CPU's work with them. †Thatís on your bread and butter stuff.

Chris is articulating MP only. †MP means that Ae essentially spawns multiple instances of itself (and renders a complete frame on that instance) and makes this determination based on a mix of available RAM and # of processors.

The OS reports to Ae the number of processors - Ae CANNOT distinguish the difference between a real CPU and an HT one. †Therefore - if spawned instances of Ae are equal to the total number of CPU's - you will have Ae instances trying to use the HT CPU's as if they were real ones.

At this point the scheduler in the OS is going to try to route traffic as efficiently as possible - however - on long renders - you will have Ae instances trying to compute on some CPU's that frankly don't exist. †This is Chris's point.

Ae attempts to take this into account with memory management and limiting the number of CPU's as one way to keep HT on and let the scheduler in the OS do the rest.

The advice from Chris is still sound - buy RAM for what is truly used. †Meaning - the amount of memory you need for previews and general computing - and the actual number of CPU's you will be using if you decide to turn on MP. †Usually that translates into - the most RAM you can possibly afford!

Hope this helps.

Adobe Systems Inc.

On Tue, Jun 12, 2012 at 2:20 PM, Greg Balint <> wrote:
Ok. So clear and final word here.

HT on will have the OS (windows) show any program that it has 12 threads to work with. Period. Right?? † Why would AE discern against it if the os doesn't even determine which threads are "originals" versus "virtuals"?

In my experience of CS5, AE just uses the Threads equally. No Delineation of whether they are virtual or not. †The performance is a little slower than if you had 12 true cores, but it's not nearly as slow as only 6 true cores.

Is this correct in Cs6 or have they removed this. I'll be sad if they have, as it actually is a faster render.

I don't care about the ray tracing engine at this point. So I'll only be using AE in a similar way as previous versions. I want my HT to be worth it!

////Greg Balint
///Art Director / Motion Graphics Designer

On Jun 12, 2012, at 5:10 PM, "Stephen van Vuuren" <> wrote:

>> As I alluded, It's only multiproc rendering that can't use virtual cores.
> Other multithreaded tasks (like non-CUDA ray-traced rendering) uses real and
> virtual cores.
> Chris, you confused about AE (which is a very rare thing). CS4 did not use
> HTT, but CS5 did - it was part of the launch marketing. Unless something has
> been disabled in CS6 which would be a big shocker and a fail since this was
> a major engineering feature of 64-bit CS5. I've been HTT rendering on almost
> every render since CS5 came out. While performance is not the same as
> physical cores - obviously - the huge cost difference, especially if you
> overclock, more than makes up. Which is why this benchmark recommended Quad
> Core, HT and MP enabled as best bang for buck using AE CS5.
> I just got my plugs setup for CS6 and will be rendering with HTT on tonight
> but I will be most surprised if it does not work.
> stephen van vuuren
> 336.202.4777
> A film is - or should be - more like music than like fiction. It should be a
> progression of moods and feelings. The theme, what's behind the emotion, the
> meaning, all that comes later.
> -Stanley Kubrick
> +---End of message---+
> To unsubscribe send any message to <>

+---End of message---+
To unsubscribe send any message to <>

Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to ListMaster