aerender: -mem_usage ceiling makes MFR drop to one frame after ~27 frames on large-raster comps - best practice for 32 GB?
After Effects 26.5, Windows 11, 16-core / 32 GB laptop with an RTX 4070 (8 GB). I render 3840x2160 comps that contain an 8848x8800 px raster as a 3D layer under a camera, using aerender, in a 32-bpc project. With -mem_usage 5 50 the first ~27 frames of a frame range render in parallel (Multi-Frame Rendering), then the working set drops from 13.7 GB to 5.3 GB while about 10 GB are still free, and frames take 8-9 s each, one at a time. After raising -mem_usage from 5 50 to 40 85 the same frames went from 9.6 to 1.8 s/frame, and a 156-frame range held about 1.3 s/frame. I also see aerender writing one ~133 MB disk-cache file per rendered 3840x2160 frame (32-bpc project) although the render settings say Disk Cache: Read Only. Questions: (1) What are the documented semantics of the two -mem_usage values (image cache percent and max memory percent) under MFR? (2) What values are recommended for 32 GB? (3) Do "RAM reserved for other applications" and "Purge every N frames" interact with aerender? (4) Is -reuse supported in 26.x? (5) How can I cut a 40-70 s start-up before the first frame for a project with about 500 comps? (6) Is the per-frame disk-cache write expected with Disk Cache set to Read Only, and is disabling the disk cache recommended for aerender? (7) Is there guidance on 32-bpc vs 16-bpc projects for Multi-Frame Rendering memory? Thank you.
