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=g1jWECgBqxjdRYjeeuCWw2SwtpdTtojrFw/+KAAZB61k9SRmmrWiSS8bvSj7ZnTKIytfl83owljUJdssN6hnZ9bB14sqpRFviIYusKFWZpcLP3Nes7STri1ffSO/pEE7;
From: Chris Meyer <chris@crishdesign.com>
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_75B5B945-EAE8-4579-AB97-9FFCAB2056E5"
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 14:28:52 -0600
In-Reply-To: <list-4745033@media-motion.tv>
To: After Effects Mail List <AE-List@media-motion.tv>
References: <list-4745033@media-motion.tv>
Message-Id: <8820A507-93CA-4787-9C8B-9AC72F8968B1@crishdesign.com>


--Apple-Mail=_75B5B945-EAE8-4579-AB97-9FFCAB2056E5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

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.=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.)

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

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 -=20
Chris=

--Apple-Mail=_75B5B945-EAE8-4579-AB97-9FFCAB2056E5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">I probably have my terminology =
on hyperthreading vs. multithreading wrong, and for that I =
apologize.<div><br></div><div>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.&nbsp;</div><div><br></div><div>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.)</div><div><br></div><div><i>Aside from =
that specific use case</i>, 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.&nbsp;</div><div><br></div><div>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.</div><div><br></div><div>Hey - I'm just trying to share some =
obscure (and unexpectedly controversial!) knowledge to help fellow users =
spend their money wisely.</div><div><br></div><div>back to work =
-&nbsp;</div><div>Chris</div></body></html>=

--Apple-Mail=_75B5B945-EAE8-4579-AB97-9FFCAB2056E5--