Because it is not just one thread ;) darktable exploits parallelization at different levels. Most, if not all modules distribute their computations automagically to different threads. Adding more concurrency by running several rendering pipes in parallel will most likely have a negative performance impact because of negative cache effects and increased overhead. Additionally, this option does only affect the thumbnail generation process. I have not observed the CPU usage during thumbnail generation, but i am assuming there is not much benefit from running it in parallel.
Regards, Markus Am 06.10.2014 um 14:43 schrieb KOVÁCS István: > Why do you limit yourself to just 1 thread? On my system (4 GB RAM, > old dual-core CPU) 2 threads work fine with 8 GB of swap space. > > On 6 October 2014 11:38, Markus Jung <[email protected]> wrote: >> Hello Bernhard, >> >> most likley, something with your darktable configuration went wrong. >> Please take a look at your core preferences: >> http://www.darktable.org/usermanual/ch06s02.html.php >> >> I am using (with the same amount of RAM): >> mipmap cache: 1536 >> background threads: 1 >> host memory limit: 4096 >> minimum single buffer size: 16 >> >> Regards, >> Markus ------------------------------------------------------------------------------ Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
