cache_memory set to huge value, based on available disk space

[kofa73]

cache_memory is set based on available disk space, without taking available RAM into account (with a few hundred GB free disk space, this would require hundreds of GB of RAM, too):

darktable/src/common/darktable.c

Lines 1656 to 1658 in a3875bd

	// set cache_memory to half of freediskspace - 4gb (eg 1gb cache_mem in case of 6gb free space)
	if(freecache > (6lu << 20))
	dt_conf_set_int64("cache_memory", (freecache - (4lu << 20))/2);

See, for example:
https://discuss.pixls.us/t/run-performance-configuration/29427/12

[kofa73]

Maybe if we can agree on a way to fix it (e.g. impose a limit of 10% of available memory, or something like that), it could be included in #11119 ?
DT_CURRENT_PERFORMANCE_CONFIGURE_VERSION may need to be incremented again.

[jenshannoschwalm]

Indeed the current stuff is wrong.
Will fix that too in #11167

[jenshannoschwalm]

@kofa73 you might want to test #11167 :-)

[jenshannoschwalm]

@kofa73 closing this?