nicehash / NiceHashMiner-Archived

NiceHash easy to use CPU&GPU Miner
840 stars 327 forks source link

my cpu doesnt appear. Says NiceHashMiner doesnt support more then 64 virtual cores... #525

Closed baalij closed 7 years ago

baalij commented 7 years ago

I have 2x Xeon 2697 v4 with 36cores and 72 threads in total. Not supported?

S74nk0 commented 7 years ago

@baalij We will make an update or a separate version that will support your CPU(s).

baalij commented 7 years ago

@S74nk0 thank you! fast reply. Do you know when you are planing to do so?

S74nk0 commented 7 years ago

@baalij Here: NiceHashMiner_NO_CPU_LIMIT.zip. Now the main reason that more than 64HT cores are disabled is because of the affinity mask. There are two files in the zip. Try first the NiceHashMiner_64HT_MASK and then NiceHashMiner_MORE_HT_MASK. I hope they can still achieve full CPU speeds (please report back your speeds). As for bench-marking I suggest you manually set lessthreads for cryptonight algorithm to 36 (or the number of the physical cores per CPU do this for both CPUs). Lowering the lessthreads for equihash might also yield a better hashrate. Please report back the speeds (if they are equal per CPU) and if both versions work (and if there are any differences in benchmarked and mining speeds, check also the stats to see if they are equal).

S74nk0 commented 7 years ago

@baalij no feedback... closing

groovadelickun commented 7 years ago

This has been working great with E7-4870 CPUs. Thank you! :) Are there any plans for more updates that support more than 64 virtual cores?

WarrenSchultz commented 7 years ago

Got a chance to borrow a big quad box for a little while to see what happened using both EXEs linked above. I've got less threads 18 set and enable_ht=true in the additional params. It throws all the work onto a single socket (with or without those parameters being set).

Here's the kicker: Benchmarking works right. If I launch a single CPU from the UI, it appears to select the CPU properly, and also ok if I kick off a second instance and let it run individually. It only seems to have issues when all four CPUs are launched from the UI at the same time. image

image