Monero Mining Performance
- Thread starter Patrick
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Yep!! LOL
Seriously thinking of downclocking it more as long as I do not loose too much, otherwise I wont be able to run it here in the summer.
I think a underclocked and undervolted FX 8 core could be a nice cheap cpu miner setup when the lower priced Ryzen cpu's are released and the older cpu's are priced to sell.
Just might pick me up a couple of cheap FX cpu's and a couple of cheap motherboards.
EDIT:
Running at 4.0 GHz and 1.30 vcore.
CPU temp is about 4-5 c lower and fans running much quieter.
Idle =118 watts
XMR-STAK-CPU only=207w
XMR-STAK-NVIDIA only =205w-218w
XMR-STAK-CPU and XMR-STAK-NVIDIA = 295w-308w
So not nearly as efficient as a E5 cpu and AMD gpu combo.
Mining xmr with FX cpu only is 1.96 hashes per watt.
Also mining xmr with a nvidia card is almost not really worth it...... 1.29 hashes per watt.
Total for this pc is 2.18 hashes per watt.
EDIT2: The older AMD chipsets run pretty hot so I may just try to run underclock the northbridge along with the cpu and lower some voltages just to see what it can do.
Last edited:
On looking at this again, 7 threads are not the optimum.
If you look at the hash rates above you see one thread is 107 H/s and two threads is only a little higher at 111 H/s then three has a big jump, then four a tiny increase on so on.
I think now that 4 threads will be ideal because it looks like when one cpu module is running one thread its running over 100 H/s when you add another thread to the same cpu module it results in a tiny increase.
So I am going to change my config to cores 1,3,5, and 7 so only one core per module is hashing.
And I expect It will run alot cooler and use noticeably less power.
AMD and their odd cache configurations. LOL
EDIT: Running 1 thread per cpu module
4 threads = 385 H/s
204 watts with just xmr-stak-cpu running, less of a decrease than what I was expecting.
And ~8c lower temperature.
Last edited:
Played around with the FX 8320 pc.
Running XMR-STAK-CPU only without XMR-STAK-NVIDIA running.
If I set the affinity to even numbered threads 0,2,4,6 it slows down to ~339 H/s.
If I change it back to use threads 1,3,5,7 it runs at ~385 H/s.
Odd.....
Running XMR-STAK-CPU only without XMR-STAK-NVIDIA running.
If I set the affinity to even numbered threads 0,2,4,6 it slows down to ~339 H/s.
If I change it back to use threads 1,3,5,7 it runs at ~385 H/s.
Odd.....
I'm betting that it will pull a bitcoin, priced low until it takes off.
With anonymity built it its designed to be used, not just speculated on like most other alt coins, now those if I was mining them I would exchange them for bitcoin every day.
So I am just mining monero and holding on to them, but I may actually purchase something eventually just to try it out and see how well it works.
Of course I could be completely wrong tho.
If there exists ccminer for AMD, then please confirm it exists (have searched for an AMD ccminer and found none.)
If the above is not true, then please list the AMD GPU results under the miner used to achieve the above results.
I've noticed today on pool.minexmr.com the difficulty has went WAY up, used to stay around 100,000 for the last three weeks now its sometime as high a ~450,000.
CPU miner:
[2017-03-26 23:10:43] : New block detected.
[2017-03-26 23:11:17] : Difficulty changed. Now: 298717.
[2017-03-26 23:11:17] : New block detected.
[2017-03-26 23:12:02] : Result accepted by the pool.
[2017-03-26 23:12:17] : Difficulty changed. Now: 448092.
[2017-03-26 23:12:17] : New block detected.
GPU miner:
[23:20:24] Thread 0, GPU ID 0, GPU Type: Ellesmere: 572.72H/s
[23:20:25] Thread 1, GPU ID 1, GPU Type: Ellesmere: 581.21H/s
[23:20:26] New job at diff 283965
[23:20:26] Thread 0, GPU ID 0, GPU Type: Ellesmere: 572.24H/s
[23:20:26] Thread 1, GPU ID 1, GPU Type: Ellesmere: 580.81H/s
How does the difficulty change the payout if at all?
CPU miner:
[2017-03-26 23:10:43] : New block detected.
[2017-03-26 23:11:17] : Difficulty changed. Now: 298717.
[2017-03-26 23:11:17] : New block detected.
[2017-03-26 23:12:02] : Result accepted by the pool.
[2017-03-26 23:12:17] : Difficulty changed. Now: 448092.
[2017-03-26 23:12:17] : New block detected.
GPU miner:
[23:20:24] Thread 0, GPU ID 0, GPU Type: Ellesmere: 572.72H/s
[23:20:25] Thread 1, GPU ID 1, GPU Type: Ellesmere: 581.21H/s
[23:20:26] New job at diff 283965
[23:20:26] Thread 0, GPU ID 0, GPU Type: Ellesmere: 572.24H/s
[23:20:26] Thread 1, GPU ID 1, GPU Type: Ellesmere: 580.81H/s
How does the difficulty change the payout if at all?
I upgraded main pc to Ryzen 1700 too. But can't get hashrate like you. Could you write, on what OS and your conf file?
Last edited:
I have Ryzen 1700 too, but can't get the hashrate as you. just 190 h. Could you show your conf file?
Solved, however got another problem. The CPU doesn't want go to max turbo boost 3.7 Ghz, just working on 3.2 Ghz. Who know where is the problem?
3.2 is default all-core turbo frequency. 3.7 is default 1 core turbo frequency.
it is setup for a 65W TDP, so its going to have lower clocks. Setting it to 3.7 all core is all but guaranteed to work, just need to make sure you keep it cool.
it is setup for a 65W TDP, so its going to have lower clocks. Setting it to 3.7 all core is all but guaranteed to work, just need to make sure you keep it cool.
@Patrick thank you so much for making this easy to deploy and test, I don't have much Linux experience so these Docker containers are great 
I'm running the Dwarfpool miner version on a spare AWS instance (d2.8xlarge w/ 36 vCPUs - Intel Xeon E5-2676v3 2.4GHz): EC2 Instance Types – Amazon Web Services (AWS)
And the hashrate is ~820 H/s which seems low, also the CPU utilisation is only around 83%.
I'm not sure what the best thread settings would be to use the way this is partitioned - any ideas?
And how can I stop and start the miner manually to test different thread settings?
Thanks again for all your help, if you put a pool together I'd definitely be interested.
I'm running the Dwarfpool miner version on a spare AWS instance (d2.8xlarge w/ 36 vCPUs - Intel Xeon E5-2676v3 2.4GHz): EC2 Instance Types – Amazon Web Services (AWS)
And the hashrate is ~820 H/s which seems low, also the CPU utilisation is only around 83%.
I'm not sure what the best thread settings would be to use the way this is partitioned - any ideas?
And how can I stop and start the miner manually to test different thread settings?
Thanks again for all your help, if you put a pool together I'd definitely be interested.
Hi @apollo69 I am on a ski slope right now checking the forums on a chair lift so I am going to take this as a to-do for later today.
The simple answer is that I am going to make an image specifically for testing this.
The AWS side is a bit tricky. You will likely not use every thread because what you are trying to do is occupy 2MB L3 cache chunks.
I will research and revert.
@4004 I hope these links work for you Best AMD RX 480 rawintensity Monero Testing and Best AMD RX 470 rawintensity Monero Testing
The simple answer is that I am going to make an image specifically for testing this.
The AWS side is a bit tricky. You will likely not use every thread because what you are trying to do is occupy 2MB L3 cache chunks.
I will research and revert.
@4004 I hope these links work for you Best AMD RX 480 rawintensity Monero Testing and Best AMD RX 470 rawintensity Monero Testing
Can someone please give me a hint on setting up xmr-stak with dual E5 cpu's.
Do you run 2 instances with "cpu_thread_num" : 10 or do you just run one?
The bit I'm confused about is getting it working optimally on a dual CPU system and using both processors.
"cpu_thread_num" : 2,
"cpu_threads_conf" : [
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 1 },
Do you run 2 instances with "cpu_thread_num" : 10 or do you just run one?
The bit I'm confused about is getting it working optimally on a dual CPU system and using both processors.
"cpu_thread_num" : 2,
"cpu_threads_conf" : [
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : false, "affine_to_cpu" : 1 },