Return-Path: Received: from gateway01.websitewelcome.com ([69.56.224.19] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4746126 for AE-List@media-motion.tv; Thu, 14 Jun 2012 00:55:41 +0200 Received: by gateway01.websitewelcome.com (Postfix, from userid 5007) id CEF8D85B24165; Wed, 13 Jun 2012 17:58:23 -0500 (CDT) Received: from ham01.websitewelcome.com (ham.websitewelcome.com [173.192.111.52]) by gateway01.websitewelcome.com (Postfix) with ESMTP id C285E85B2413B for ; Wed, 13 Jun 2012 17:58:23 -0500 (CDT) Received: by ham01.websitewelcome.com (Postfix, from userid 666) id C3A316DF5B29F; Wed, 13 Jun 2012 17:58:23 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on ham01.websitewelcome.com X-Spam-Flag2999: NO X-Spam-Level2999: X-Spam-Status2999: "No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE autolearn=ham version=3.3.1 Received: from alpina.websitewelcome.com (alpina.websitewelcome.com [74.54.176.2]) by ham01.websitewelcome.com (Postfix) with ESMTP id 4151D6DF5B18B for ; Wed, 13 Jun 2012 17:58:23 -0500 (CDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=crishdesign.com; h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-BWhitelist:X-Source:X-Source-Args:X-Source-Dir:X-Source-Sender:X-Source-Auth:X-Email-Count:X-Source-Cap; b=FeNRrk0e4dE1YDE+PZeGKCSUfnOx12EKzHjkiujMbS9vhJN2dBbCBwQHC4EkQpdTse1Z/Hf/aRuEFeuJbkn4Y20wF+TWvkpYM+GgClsZb6x6fH/hl/P9GUxAmFjSCBJj; Received: from [199.21.106.94] (port=52751 helo=[192.168.0.7]) by alpina.websitewelcome.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1SewW6-0003da-RF for AE-List@media-motion.tv; Wed, 13 Jun 2012 17:58:23 -0500 From: Chris Meyer Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/alternative; boundary="Apple-Mail=_7A13D188-ABD0-4336-8BF2-9E8389BE3441" Subject: Re: [AE] (OT) An example of a PC version of a Mac Pro with today's tech for AE Date: Wed, 13 Jun 2012 16:58:22 -0600 In-Reply-To: To: "After Effects Mail List" References: Message-Id: <8CDB02AD-43DC-4A5F-9A79-A4167B013522@crishdesign.com> X-Mailer: Apple Mail (2.1278) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - alpina.websitewelcome.com X-AntiAbuse: Original Domain - media-motion.tv X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crishdesign.com X-BWhitelist: no X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: ([192.168.0.7]) [199.21.106.94]:52751 X-Source-Auth: chris@crishdesign.com X-Email-Count: 1 X-Source-Cap: Y3Jpc2h3ZWI7Y3Jpc2h3ZWI7YWxwaW5hLndlYnNpdGV3ZWxjb21lLmNvbQ== --Apple-Mail=_7A13D188-ABD0-4336-8BF2-9E8389BE3441 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii You may be seeing individual functions in After Effects take advantage = of multiple cores, regardless of how many "CPUs" you've assigned for = background rendering. When I have multiprocessing disabled, I still see = 12 of my cores pop when I do a normal "single CPU" preview. - Chris On Jun 13, 2012, at 3:49 PM, Greg Balint wrote: > Forgive me for the constant questioning of this statement from the = product manager, but if I have a 6 core cpu with hyperthreading on, and = I can choose in the preferences to use 9 cores, and it launches 9 = separate processes in my OS with 2 Gb of RAM reserved for each. And I = can see those processes all running when I render, and those 9 "cores" = that windows or OSX shows are all maxed out at 100% usage, and the = render shows 9 frames at a time being rendered in chunks, how is AE only = using the 6 physical cores and not also utilizing the extra cores = available due to hyperthreading? >=20 > By the statement made, Wouldn't I see only 6 of them pegged at 100% = usage, while the other 6 aren't doing anything? >=20 > ////Greg Balint > ///Art Director / Motion Graphics Designer > delRAZOR.com/ >=20 > On Jun 13, 2012, at 4:28 PM, Chris Meyer = wrote: >=20 >> I probably have my terminology on hyperthreading vs. multithreading = wrong, and for that I apologize. >>=20 >> But this does not change the fact - confirmed by the AE product = manager, fer crissakes - that when you enable the preference for = multiprocessor rendering, this specific feature can only really use the = physical cores, and one should not spend more than needed buying RAM = strictly to feed virtual cores during multiprocessor rendering, as you = won't see a gain.=20 >>=20 >> To give an example: With my 12 real + 12 virtual core Mac (which the = OS reports as being 24 cores), a sweet spot would have been 36 or so GB = of memory so I could reserve the recommended 3 GB per 10 cores = (reserving 2 cores and 6 GB of RAM for other functions), rather than = spending money to install (22 x 3) + 6 =3D 72 GB when it would not be = taken advantage of for multiproc rendering. (Me, I underspent and only = put 24 GB in it, riffing on outdated recommended practices that you only = needed 1.5 or maybe 2 GB per process. I regret that, as I'm not getting = the multiproc boost I should have. OTOH, running two Quadro 4000 cards = has been nice, but that's a separate well-tread discussion.) >>=20 >> Aside from that specific use case, in general more RAM is good (esp. = for large format work like SV2's, as well as more caching etc.), and = more cores - both real and virtual - are good to accelerate other parts = of the program. I never said otherwise.=20 >>=20 >> I understand various people have real empirical data that changing = certain numbers gave certain results, and I don't dispute that. But = there's a difference between speculating at how the two may be = connected, and learning what is actually going on underneath the hood. >>=20 >> Hey - I'm just trying to share some obscure (and unexpectedly = controversial!) knowledge to help fellow users spend their money wisely. >>=20 >> back to work -=20 >> Chris --Apple-Mail=_7A13D188-ABD0-4336-8BF2-9E8389BE3441 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii You = may be seeing individual functions in After Effects take advantage of = multiple cores, regardless of how many "CPUs" you've assigned for = background rendering. When I have multiprocessing disabled, I still see = 12 of my cores pop when I do a normal "single CPU" = preview.

 - = Chris



On Jun 13, 2012, = at 3:49 PM, Greg Balint wrote:

Forgive me for the constant questioning of this = statement from the product manager, but if I have a 6 core cpu with = hyperthreading on, and I can choose in the preferences to use 9 cores, = and it launches 9 separate processes in my OS with 2 Gb of RAM reserved = for each. And I can see those processes all running when I render, and = those 9 "cores" that windows or OSX shows are all maxed out at 100% = usage, and the render shows 9 frames at a time being rendered in chunks, = how is AE only using the 6 physical cores and not also utilizing the = extra cores available due to hyperthreading?

By = the statement made, Wouldn't I see only 6 of them pegged at 100% usage, = while the other 6 aren't doing anything?

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

On = Jun 13, 2012, at 4:28 PM, Chris Meyer <chris@crishdesign.com> = wrote:

I probably = have my terminology on hyperthreading vs. multithreading wrong, and for = that I apologize.

But this does not change the fact - = confirmed by the AE product manager, fer crissakes - that when you = enable the preference for multiprocessor rendering, this specific = feature can only really use the physical cores, and one should not spend = more than needed buying RAM strictly to feed virtual cores during = multiprocessor rendering, as you won't see a = gain. 

To give an example: With my 12 real = + 12 virtual core Mac (which the OS reports as being 24 cores), a sweet = spot would have been 36 or so GB of memory so I could reserve the = recommended 3 GB per 10 cores (reserving 2 cores and 6 GB of RAM for = other functions), rather than spending money to install (22 x 3) + 6 =3D = 72 GB when it would not be taken advantage of for multiproc rendering. = (Me, I underspent and only put 24 GB in it, riffing on outdated = recommended practices that you only needed 1.5 or maybe 2 GB per = process. I regret that, as I'm not getting the multiproc boost I should = have. OTOH, running two Quadro 4000 cards has been nice, but that's a = separate well-tread discussion.)

Aside from = that specific use case, in general more RAM is good (esp. for large = format work like SV2's, as well as more caching etc.), and more cores - = both real and virtual - are good to accelerate other parts of the = program. I never said otherwise. 

I = understand various people have real empirical data that changing certain = numbers gave certain results, and I don't dispute that. But there's a = difference between speculating at how the two may be connected, and = learning what is actually going on underneath the = hood.

Hey - I'm just trying to share some = obscure (and unexpectedly controversial!) knowledge to help fellow users = spend their money wisely.

back to work = - 
Chris
<= br>
= --Apple-Mail=_7A13D188-ABD0-4336-8BF2-9E8389BE3441--