![]() You'll need to experiment I set this to 800 with my 6GB NVidia card. If you set it too high, darktable won't make full use of your GPU memory, and will not run as fast as possible. If you set this too low, darktable will try to allocate more GPU memory than what is available, will fail to do so, and fall back to the CPU. This specifies how much GPU memory darktable should assume is already taken by your operating system and anything else you have running (browser, etc.). See /darktable-org/darktable/issues/10910.įor OpenCL, the most important parameter is probably opencl_memory_headroom. ![]() So, for example:įor 8 GB of RAM, set 4 - 6 GB (4096 - 6144 MB) ![]() Or you could subtract 2 - 8 GB from the main memory size, based on your usage. I'd suggest that you set 75-80% of your installed (main) memory size - more if you have over 32 GB installed. You may be able to speed up darktable, especially exports, by rasing the parameter host_memory_limit (on the UI: preferences (cogwheel icon) -> processing -> host memory limit (in MB) for tiling)). Some new darktable modules, especially when processing images with today's high-resolution cameras, need lots of memory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |