![]() ![]() A solid-state drive can ease the pain slightly. We have positive reports that this functions well for several users, but it still might get extremely slow for others. However, you this could cause your system to “thrash”, as it reads or writes data pages to and from the hard disk. ![]() Theoretically, you could run darktable with lower amounts of physical RAM and balance this with enough swap space. We suggest that you have a least 4GB of physical RAM plus 4 to 8GB of additional swap space installed. □total system memoryįrom the above analysis, it is evident that your computer needs a sane memory setup to properly run darktable. On top of that we have darktable’s code segment, the code and data of all dynamically linked system libraries, and not to forget, further buffers where darktable stores intermediate images for quick access during interactive work (mip map cache).Īll in all, darktable needs a minimum of about 4GB of memory to run happily. Without further optimization, anything between 600MB and 3GB would be needed merely to store and process image data. If we have a more complex module, its algorithm might additionally require several intermediate buffers of the same size. As we want to process the image, we will at least need two buffers for each module – one for input and one for output. ![]() Each full image of this size will therefore need about 300MB of memory. If you have a 20MPx image then, for precision reasons, darktable will store this internally as a 4 x 32-bit floating point cell for each pixel. Darktable’s memory requirements are high. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |