If Coffeelake has a design quirk that can be worked around in software
such a workaround would probably have a negative effect on other models. If it's a coffee lake issue it needs a Coffeelake fix.
I suppose that populating scrypt algo parameters to command line can help a lot, if yescript, like regular scrypt, can be calced with different algo presets (precache amount, link split size and so on), then coffeelake make take profit from better cache-fitting splitting.
Anyway tomorrow i'll try to recompile miner with different presets in scrypt.c
Again I speculate but maybe the
compiler isn't yet tweaked for Codffeelake. What version did you compile with?
i currently use windows precompiled versions on both 5820 and 8700, tomorrow i'll try latest gcc with skylake opt flag, but i suppose that compiler won't make any changes inside asm instruction so opt flag won't help, at least a lot.
You stated lower performance with fewer threads.
That is mostly windows problem - with 6 threads it uses only 3 physical cores and 3 ht cores - clearly seen with cputemp - after start of 6 threads, 3 cores start to generate heat (70-75C on busy ones, 45C on spare) and shows 100% load, with 12 threads all cores are hot and busy
Under ubuntu difference is within the margin of error
I suggest you try other algos with 6 and 12 threads to get a more complete profile. If some algos are affected more than others
it may reveal a pattern.
yep, i'll try