Participant

Question

After effects multiprocessor render not using full CPU

Forum|Forum|4 years ago
October 27, 2021
3 replies
8113 views

I've got a 32 core threadripper with 256gb ram 10gb graphics card

running after effects beta, just installed.

Have it set to multiprocessor render.

while rendering, either on render cue or media encoder:

Max cpu use around 45% but consistently around 18%

RAM usage around 30 - 50%

GPU usage around 1-2%

On my smaller machine - 6 core, 64gb ram, I was hitting close to 100 percent CPU usage.

I'm exporting PNG sequences from After Effects, tried quicktime and not much difference.

Any ideas of how to get all 32 cores working?

B

bgbmpanic

Participant

Still a problem nowadays.

Figured out a fix for myself: disabling the disk cache. It dramatically increases the render speed. Seems like even the m.2 SSD is the bottleneck

So I'm disabling it for renders and enabling it when I tweak and preview.

Ryzen 9 5950X
32GB RAM
3060 12 GB

Disk cache drive: 256 GB
Drive Controller: NVMe (PCIe x4 8.0 GT/s @ x4 5.0 GT/s) (HWinfo64)

Szalam

Community Expert

Try the benchmark project mentioned here: Multi-Frame Rendering is here! (AKA The multithrea... - Adobe Support Community - 11885358

Render it with MFR off and then render with MFR on. (Make sure you clear the cache between your test attempts.) You should see a noticable difference between the two times.

Then it'll just be a matter of learning how to optimize projects to take advantage of MFR functionality.

bennettjonesAuthor

Participant

awesome - thank you!

Mylenium

Legend

Sorry, but without any info about the actual project contents and other details like actual render settings, storage locations, cache settings and whatnot that is a bit of a hollow statement. Even with MFR the rules don't change much: There's a million factors that define how AE renders what and the limitations that apply e.g. to GPU acceleration apply just as well. A simple incompatible effect, combinations of layer switches, certain types of pre-composing, time-remapping and whatever you can imagine forces AE back into snail mode can be relevant here. And even if it seems to fly on one machine may still mean it simply has exhausted its capabilities on another machine with more cores. This can go as far as some underlying code libraries simply not being made to use more than X thereads or to be instanciated in a fashion compaitible with all manner of parallel processing such as MFR sort of is.

Mylenium

M

MikeyDee7000

Participating Frequently

I also have this MAJOR problem with MTR. I don't care what excuses Adobe makes for not having addressed this issue. Non-compatible effects, non this and that, blah blah blah. The engineers at Adobe need to step up and address this issue. I also have a 32 core threadripper beast, and it is simply inexcusable that not all my processors are being used. People like us buy expensive machines in order to speed up workflow, only to be slowed down by inefficient programming. I don't care what problems Adobe engineers have, all I know is that their inability to provide effective multi-rendering in 2023 is ridiculous. Your team of engineers needs to resolve this imediately.

M

MikeyDee7000

Participating Frequently

Furthermore it's pointless to provide people with your "benchmark" project. Who cares about your benchmark project? It's not your benchmark project we're trying to render, it's our own projects that need to be rendered, so instead of sending useless benchmark projects, why don't you guys solve this issue to work on all projects? Logical no?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded