I was under the impression that using more threads than cores on a high core machine (aka 8/16) is only really useful for code that's very CPU intensive and not memory/cache intensive, because otherwise the memory bandwidth becomes the bottleneck.
Alain
Alain
That depends on what you are doing. Printing, thumb, and raw building are all CPU intensive. Printing speed benefits from more threads in particular because printing is not very memory intensive as most of the time is spent interpolating pixels which is done in small chunks (tiles) to be very efficient and these are split up among threads. Raw building can be memory intensive if you are building raws from cameras with a high pixel count but QU already takes care of that by monitoring memory usage during raw (cache) development and only using the number of threads necessary. But even with raw building, most of the job is CPU intensive with color channel interpolation and building the final image.
Example: On a 12 core/24 thread machine, printing a single 24x36 inch print took 27 seconds with 2020.109 (which supported up to 8 threads). With 2020.110, the same print took 19 seconds to process; proportional to the extra threads (12). Not particularly relevant for a single 24x36 inch print, but what if you had 10 of them to print? Or 20? Or a hundred 8x10 prints?
Mike
Thanks (Although you write about extra cores, not extra CPU threads.)