Does Capture One like cores/threads?
Does Capture One have a sweet spot in the number of cores/threads or can it effectively use any number thrown at it as some software see diminishing returns or negative effect when it gets too lean from spreading out to all the threads.
Phase One, have you been testing out Ryzen and Skylake-X builds?
Phase One, have you been testing out Ryzen and Skylake-X builds?
0
-
As long as not a C1-Stuffmember answers:
I have an R7 1700 Ryzen. C1 seems to work with up to 16 Threads. During importing I can also work on my RAW-Files; even if I have a lot of software in the background running (like scanning DAM-Software, Desktop-Search indexing).
For a example, look in this thread. I posting screenshot from the task-manager during importing on working with RAW-Files.0 -
Yepp, on Ryzen 7 it occupies and use all 8 /16 cores/threads.
And Threadrypper is comming with 16/32 of it - as well as Intel's core i9 (later and more pricey) or Epyc server platform with up to 32/64 on single socket.
Key point of interest is a influence of AVX2 and AVX512 instructions in C1's code - 256bit AVX executes differently on AMD architecture and AVX512 is not supported at all. All other IPC performance is great on AMD Zen architecture.0
Post is closed for comments.
Comments
2 comments