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