From: "Brendan Bolles" Received: from nail.lmi.net ([66.117.140.18] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6363975 for AE-List@media-motion.tv; Wed, 29 Nov 2017 22:58:18 +0100 Received: from [192.168.1.20] (unknown [12.42.42.62]) by nail.lmi.net (Postfix) with ESMTPA id D9584E435F for ; Wed, 29 Nov 2017 14:02:00 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: [AE] New AE script- Rendergarden In-Reply-To: Date: Wed, 29 Nov 2017 14:01:42 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <51CDAC1E-08CC-4265-B4B2-3949ED0E196D@fnordware.com> References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1085) On Nov 29, 2017, at 1:32 PM, Stephen van Vuuren wrote: > So if I understand this, it may not really do what I need. Here's a = typical render going right now, eating about 100GB of 128GB machine. = https://photos.app.goo.gl/8J77BXrE1U9oio2m2 AE 2014 is configured 12 = threads, 8 GB per thread. >=20 > If I created 12 processes with Render Garden, the first will likely = take a ton of memory, next will take what's left and then what happens? In my experience, the threads will eventually even out. The first = process may be able to grab more memory before the other ones start = demanding it, but when all of them start demanding memory, the Adobe = memory management will tend to have them share it equally. It's pretty = clever, actually. Granted, my testing has been on newer versions of AE, so I don't know if = it works differently in 2014. Like I said, you can add the -mem_usage = argument to the command line template if you think it will help. Brendan