| ||||||||||
| 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. I just don't want someone saying "I've got a 12 physical core machine, plus 12 virtual cores, times 3 gig per proc for multiproc rendering, hey - I need to buy at least 72 GB of RAM for this machine to max out its performance!" For multiproc rendering, it's more like 12 physical cores, minus 2-3 reserved for the system and other functions, times 3 gig, plus leaving a little left over for the other processes - more like 32 GB (probably 48, if you arrange the RAM as 3 sets for the 3 memory channels of a 12-core machine). Then take the money you saved and put it toward an NVIDIA GPU (if you're doing a lot of ray tracing) or an SSD for the cache (which will speed up retrieving previously-done work). - Chris On Jun 12, 2012, at 2:27 PM, Greg Balint wrote: > Well this is quite odd. I've been using hyperthreaded AE multiprocessing in CS5 on PC, no problem. Windows shows all processes expected and All cores and "threads" running at full potential. Is it faking this for show or something? Or does cs6 start the trend of not using hyperthreaded cores? > > Hyperthreading always yielded faster results vs same clock speeds non-hyperthreaded for me. Only overclocking can show faster benchmarks when hyperthreading is off. Which is the only reason I would ever turn it off. > > Did I just read this wrong or something? > > I have a 6core i7 980. If I render without hyperthreading on, I can only use 4-5 cores. If I have HT on, I can use up to about 9 cores with the amount of RAM i have, and it definitely readers faster. All 9 threads show rendering at 100% CPU load on task manager. > > ////Greg Balint > ///Art Director / Motion Graphics Designer > delRAZOR.com/ > > On Jun 12, 2012, at 2:02 PM, Chris Meyer <chris@crishdesign.com> wrote: > >> On Jun 12, 2012, at 11:29 AM, Rob & Jenny wrote: >> >>> (16 hyperthreaded cores) >> >> BTW, I have been told by Steve Forde that AE's multiproc rendering only uses physical cores, not the virtual ones. The OS might assign a virtual one, but it won't process, and AE will eventually recognize this and try to assign another one. That's not to say virtual cores aren't of use elsewhere; just a heads-up for someone who may, say, feel compelled to also buy enough RAM to feed cores AE won't actually use. >> >> - Chris >> >> >> >> +---End of message---+ >> To unsubscribe send any message to <ae-list-off@media-motion.tv> >> > > +---End of message---+ > To unsubscribe send any message to <ae-list-off@media-motion.tv> |
