Sorry, I couldn’t convince myself to learn to use gops.
You mentioned that Windows shuffles the threads between the cores, so I’ve set the CPU affinity of the duplicacy process to 2 cores. It doesn’t even fully utilize 2 cores. The graph doesn’t change if I use -threads 4 option.
Edit: with affinity set to single core:
Yeah, it’s probably using one core, not two. Look at complementary valleys and peaks. Try setting affinity to 1.
But I guess what @sevimo says here is likely a culprit.
As a test you might want to build custom duplicacy with that change and see if this resolves the performance issue. But ultimately the solution shall come from @gchen, after complete testings.
