Return-Path: Received: from mail-ie0-f173.google.com ([209.85.223.173] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5278479 for AE-List@media-motion.tv; Fri, 08 Nov 2013 07:37:18 +0100 Received: by mail-ie0-f173.google.com with SMTP id x13so8100ief.32 for ; Thu, 07 Nov 2013 22:38:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=P3JJ8ifJ1OfNzSaUS1JASClLzp03fqMS8+RV2CCA9+4=; b=tPrezSb9sNKF4RAp1ubc98J7DKZ0DqSPnKPUpy0Ii4Z1gpmjGMLmEi2+3Xuvj3ZtBz +YOiRTmhGspDZ5bQy/iEGv8xlU61cUkm7hQivGN0K3kpMcXA93pCdp7WCa+edKajwkkj xRN/k+ev9/wQwXdyEbTSSo+lPg51mb3+yalI6Q8uhJPsAz3wfUPndp0+Bqxzo5vj5pp0 kMzC5Fn9jYX+s0byd2LZnQ+fyl+lH9umcUucG3ibh3Dv3Yq5pWEFRP75krw8k6Cuu2nQ UrP+Dw0hfPGDSYqBIK0BBb+b6uzhky72BQhS/cXR7n9h93jEnCm1jesKkQXAsGLKwQjA WDBg== MIME-Version: 1.0 X-Received: by 10.42.67.74 with SMTP id s10mr8020177ici.1.1383892734571; Thu, 07 Nov 2013 22:38:54 -0800 (PST) Sender: meomimurphy@gmail.com Received: by 10.64.62.36 with HTTP; Thu, 7 Nov 2013 22:38:54 -0800 (PST) Date: Thu, 7 Nov 2013 22:38:54 -0800 X-Google-Sender-Auth: 7dqTSZBtwnRpmB4313zkW4R-59g Message-ID: Subject: Multiprocessing and RAM previews? From: Michael Murphy To: After Effects Mail List Content-Type: multipart/alternative; boundary=485b397dd259da842f04eaa4a243 --485b397dd259da842f04eaa4a243 Content-Type: text/plain; charset=ISO-8859-1 Hi everyone, I had a question to you all regarding your use of multiprocessing in AE CS6+. I've used AE on about 4 different machines in the last few years, with both flavors of OS, all with either 16 or 32 gigs of ram. I've configured my multiprocessing prefs, according to Todd Kopriva's Adobe videos and posts (i.e. making sure I'm not starving the system and other apps, giving 2-3 gigs of ram per cpu etc.). What I've found on all these systems is that using multiprocessing during ram previews actually seems to take longer than without. There's a variable (but what always feels like a very long) wait as the background processes fire up that seems to nullify the speed benefits once the extra cpu's do kick in. I've also found that the disk cache seems a bit more flakey with multiprocessing enabled (i.e. doesn't seem to cache all the time). I have invariably ended up just turning multiprocessing off and only using it for final renders (and usually not even then as I often render over night when render time isn't an issue). So my question is, has everyone else had a similar experience? I haven't seen anyone mention it on the list, so I've always thought It might be a anomaly with my configuration, but I have a new computer now, running Win 8.1 pro 64bit and it's the same situation as my 2012 macbook pro and older systems. Thanks for your input! mm --485b397dd259da842f04eaa4a243 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi everyone,

I had a question to you al= l regarding your use of multiprocessing in AE CS6+.

I've used AE on about 4 different machines in the last few years, wit= h both flavors of OS, all with either 16 or 32 gigs of ram. I've config= ured my multiprocessing prefs, according to Todd Kopriva's Adobe videos= and posts (i.e. making sure I'm not starving the system and other apps= , giving 2-3 gigs of ram per cpu etc.).

What I've found on all these systems is that using = multiprocessing during ram previews actually seems to take longer than with= out. There's a variable (but what always feels like a very long) wait a= s the background processes fire up that seems to nullify the speed benefits= once the extra cpu's do kick in. I've also found that the disk cac= he seems a bit more flakey with multiprocessing enabled (i.e. doesn't s= eem to cache all the time).

I have invariably ended up just turning multiprocessing= off and only using it for final renders (and usually not even then as I of= ten render over night when render time isn't an issue).

So my question is, has everyone else had a similar experience? I= haven't seen anyone mention it on the list, so I've always thought= It might be a anomaly with my configuration, but I have a new computer now= , running Win 8.1 pro 64bit and it's the same situation as my 2012 macb= ook pro and older systems.

Thanks for your input!

mm
--485b397dd259da842f04eaa4a243--