Exports, the Render Queue and command-line renders use the memory budget (#3941)

The command-line tool reads the system's memory once at start, so its caches
share the budget of the installed RAM instead of the budget for unknown RAM.
A Render Queue run's two layer caches and a one-off export's own caches take
the session's layer cache budget instead of a fixed 512 MiB; they are in the
memory accountant, which keeps them within the common budget together with the
other caches. In the browser each gets half the layer cache's cap.
This commit is contained in:
vangel76 committed 2026-11-19 10:29:54 +01:00
1 parent 6bea5fa6ae
commit 0d9c69563f
10 files changed
+149 -18

No files matched your search

+4 -3
View File
@@ -470,10 +470,11 @@ fn backend(args: &Args, default_demo: bool) -> Result<Backend, Failure> {
Ok(b)
}
/// A wired session; `--gpu` attaches the GPU compositor (renders then follow the project's
/// renderer setting, GPU Acceleration by default).
/// A wired session whose caches share the budget of the installed RAM (#3941); `--gpu` attaches
/// the GPU compositor (renders then follow the project's renderer setting, GPU Acceleration by
/// default).
fn session(args: &Args) -> Result<effectcraft_engine::Session, Failure> {
let mut s = effectcraft_host::session();
let mut s = effectcraft_host::headless_session();
if args.flag("--autosave") {
let dir = effectcraft_host::config_dir().ok_or_else(|| Failure::Error("--autosave: no config directory; set EFFECTCRAFT_CONFIG_DIR".into()))?;
// Read only auto-save settings. Opting in must not change headless rendering or load