Windows Defender quarantining and removing xmr-stak files<\/a>, but that wasn’t the problem.<\/p>\nI then began to check and compare the config and cpu txt files. And I found the issue!<\/p>\n
Here was the incorrect cpu.ini file configuration on the server with the lower-than-expected hash rate:<\/p>\n
“cpu_threads_conf” :
\n[
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 0 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 2 },<\/h4>\n],<\/h4>\n
And here is the cpu.ini file conf from the well performing hash rate server:<\/p>\n
“cpu_threads_conf” :
\n[
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 0 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 2 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 4 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 6 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 8 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 10 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 1 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 3 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 12 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 14 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 16 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 18 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 20 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 22 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 13 },
\n{ “low_power_mode” : false, “no_prefetch” : true, “affine_to_cpu” : 15 },<\/h4>\n],<\/h4>\n
Quite a big difference! What I hadn’t realised is that when you first run xmr-stak on a new machine, after unzipping the package, a wizard runs. I thought this wizard simply collected information about your mining pool, wallet id, pool password, tls\/ssl support and nicehash support. However, it does one more important thing. It analyses your computer, and sets the configuration files appropriately. If you have a dual-core low-end CPU, it will assign the cpu thread configuration appropriately. If you have a super powerful dual-socket Xeon, it will likely assign many more threads.<\/p>\n
I was lazy. I had copied my full pre-configured xmr-stak-win64 folder from my laptop (dual core crap CPU) to the Xeon server and simply executed the hashing process. I wasn’t keen to complete the full wizard and thought this was a good time saving approach. The Xeon server had 2 threads configured, rather than the 16 threads that the wizard would normally pick.<\/p>\n
If you have any doubts about your current xmr-stak configuration, or if your system has changed in any way, you can delete the config.txt and cpu.txt files to envoke a new wizard prompt, where you can re-enter all of your details, and get your threads reassessed.<\/p>\n
The final though on the cpu.txt file is that you can change the thread settings manually, if you believe that you can achieve a more effective distribution of hashing load on your CPU. Personally, I haven’t been able to beat the wizard-generated settings.<\/p>\n
Happy mining!<\/p>\n","protected":false},"excerpt":{"rendered":"
Recently I wrote about mining\u00a0and compared the hashrate of all my computers\/servers at home (CPU and GPUs). My current goal is to mine 1 whole monero coin, and two weeks into the project, I’ve mined 0.134 of a coin. Yesterday I noticed a discrepancy between two very similarly equipped mining computers. One of the hash<\/p>\n
<\/span>Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":266,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[27,16],"tags":[33,31,30,49,34,39,36,38,37,32,28,29,35],"_links":{"self":[{"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/posts\/258"}],"collection":[{"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/comments?post=258"}],"version-history":[{"count":9,"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/posts\/258\/revisions"}],"predecessor-version":[{"id":275,"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/posts\/258\/revisions\/275"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/media\/266"}],"wp:attachment":[{"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/media?parent=258"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/categories?post=258"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/iblogit.net\/index.php\/wp-json\/wp\/v2\/tags?post=258"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"\"](\"http:\/\/iblogit.net\/wp-content\/uploads\/2018\/01\/mining-crypto-in-summer-1024x950.png\")
<\/p>\n![\"\"](\"http:\/\/iblogit.net\/wp-content\/uploads\/2018\/01\/xmr-miner-dir.png\")
<\/p>\n