Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1390. (Read 6590718 times)
April 16, 2016, 08:44:55 PM
After a few hours, I am at <1% DCR rejects on stratum. No change to ethash output. Big improvement from 20-30% rejects with http getwork.
April 16, 2016, 08:28:16 PM
I'm using this cmdline with the new version:
After 3 hours, my ETH shares decreased about 5% but my DCR efficiency is now at above 98%.
So, the results are promising and I'll give this new version some more hours to test it's stability.
Note: I'm using 6 270X, a 7870 and two 7950s, thus a mix of Pitcairn and Tahiti cards.
@Claymore: I'm looking forward to test your 270x optimized code!
Code:
EthDcrMiner64.exe -epool eth-us.dwarfpool.com:8008 -ewal 0x2c988a9d1b730520ad270ed0ec68a77dbe2f0264/PC -epsw x -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal Trimegisto.PC -dpsw x -tt 75 -dcri 20 -r 0
After 3 hours, my ETH shares decreased about 5% but my DCR efficiency is now at above 98%.
So, the results are promising and I'll give this new version some more hours to test it's stability.
Note: I'm using 6 270X, a 7870 and two 7950s, thus a mix of Pitcairn and Tahiti cards.
@Claymore: I'm looking forward to test your 270x optimized code!
April 16, 2016, 08:25:33 PM
ethminer--cointron-- 15mh\s
claymore--11mh\s why? (R7 370)
claymore--11mh\s why? (R7 370)
same 4x r7 370
qtminer : 60mh/s
claymore : 55mh/s
April 16, 2016, 06:27:39 PM
ethminer--cointron-- 15mh\s
claymore--11mh\s why? (R7 370)
claymore--11mh\s why? (R7 370)
April 16, 2016, 06:03:23 PM
After 1 hour on sprnova Decret stratum protocol i got from 2-3%. Very nice.
April 16, 2016, 05:23:56 PM
Hello any example for coinotron?
Check OP or readme.
EthDcrMiner64.exe -epool coinotron.com:3344 -ewal Redhex.rig1 -esm 2 -epsw x -dpool http://dcr.suprnova.cc:9111 -dwal Redhex.my -dpsw x -allpools 1
Redhex.rig1 is a wallet?
It is username.workername
April 16, 2016, 05:17:00 PM
Hello any example for coinotron?
Check OP or readme.
EthDcrMiner64.exe -epool coinotron.com:3344 -ewal Redhex.rig1 -esm 2 -epsw x -dpool http://dcr.suprnova.cc:9111 -dwal Redhex.my -dpsw x -allpools 1
Redhex.rig1 is a wallet?
April 16, 2016, 05:09:01 PM
Thank you. I've testing v 2.0 now. Got above 10% Rej from zpool-stratum (DCR). Trying sprnova stratum (DCR), and it looks much better, about 3%. Need more time for better numbers. What about solo version, i am waiting ))
Let me implement most important features for pool version firstly, I think it will take 1-2 weeks.
April 16, 2016, 05:07:03 PM
It's not all about hash, more important are shares submitted.
Because miners, calculators, and pools all seem to have slightly different ideas about the hashrates rigs actually generate, the truest measure of gpu mining ability is how much ethereum is paid over time. In my rigs, running the Claymore instead of Ethminer, I get more pay.
But effective hash rate depends to some degree on luck, right? What pool are using now?
I'm at ethermine.org . Luck does make variance though the more time involved the less luck impacts anything. I ran for 24 hours. Since the miner hasnt yet existed for a week its difficult to give longer trials. Revisiting my first rig report found that over 2-days it was then gaining very slightly less than using just the first days data, but close enough to be giving a pretty accurate picture of whether this miner was giving more ethereum than ethminer.
Check my post right before yours. Both miners are generating pretty much the same amount of money.You cant make good comparison if you run the miners one after another. They should be on equals rigs, same time, same pool as I did.
I agree your way is a greater scientific methodology, but I disagree that good comparisons can't be made any other ways. Given that the previous value of daily hashrate is well known and time proven, making just the one change of switching mining software does create a valid comparison between the two. While the new higher hashrate }could{ be a fluke result, todays addition 24 more hours of data, along with multiple others reporting similar results, suggest it is not a fluke at all.
Perhaps you are using cards that Claymore doesnt give a benefit to? We dont know because nobody has compared the new improvement results across all gpu versions, other than we know 270s dont function well with it yet.
I'm using r9 380, dont know if they are optimized. I updated the miner and now the links i gave are original qtminer vs Claymore eth-proxy method.
April 16, 2016, 05:02:43 PM
Thank you. I've testing v 2.0 now. Got above 10% Rej from zpool-stratum (DCR). Trying sprnova stratum (DCR), and it looks much better, about 3%. Need more time for better numbers. What about solo version, i am waiting ))
April 16, 2016, 05:01:23 PM
Hello any example for coinotron?
Check OP or readme.
April 16, 2016, 04:51:30 PM
Hello any example for coinotron?
April 16, 2016, 04:31:24 PM
Nice work Claymore, thank you for frequent updates.
Any updates on 270/X, the "weak" cards?
Any updates on 270/X, the "weak" cards?
I'm still working on it, also on improvements for Fury cards.
April 16, 2016, 04:26:14 PM
Nice work Claymore, thank you for frequent updates.
Any updates on 270/X, the "weak" cards?
Any updates on 270/X, the "weak" cards?
April 16, 2016, 04:19:13 PM
It stops immediately, you can see that miner sends a share, then gets new job, then pool sends "rejected" answer. The problem is on pool - I see sometimes it takes pool about 3-5 seconds to send "accepted" response for share sent. If pool gets new block within this time it sends "rejected".
What stratum DCR pool would you recommend to use with your miner?
Currently I use supronova though it does not support vardiff, it may cause problems if everyone starts using this pool. May be they will fix it.
April 16, 2016, 04:17:51 PM
It stops immediately, you can see that miner sends a share, then gets new job, then pool sends "rejected" answer. The problem is on pool - I see sometimes it takes pool about 3-5 seconds to send "accepted" response for share sent. If pool gets new block within this time it sends "rejected".
What stratum DCR pool would you recommend to use with your miner?
April 16, 2016, 04:13:16 PM
It's not all about hash, more important are shares submitted.
Because miners, calculators, and pools all seem to have slightly different ideas about the hashrates rigs actually generate, the truest measure of gpu mining ability is how much ethereum is paid over time. In my rigs, running the Claymore instead of Ethminer, I get more pay.
But effective hash rate depends to some degree on luck, right? What pool are using now?
I'm at ethermine.org . Luck does make variance though the more time involved the less luck impacts anything. I ran for 24 hours. Since the miner hasnt yet existed for a week its difficult to give longer trials. Revisiting my first rig report found that over 2-days it was then gaining very slightly less than using just the first days data, but close enough to be giving a pretty accurate picture of whether this miner was giving more ethereum than ethminer.
Check my post right before yours. Both miners are generating pretty much the same amount of money.You cant make good comparison if you run the miners one after another. They should be on equals rigs, same time, same pool as I did.
I agree your way is a greater scientific methodology, but I disagree that good comparisons can't be made any other ways. Given that the previous value of daily hashrate is well known and time proven, making just the one change of switching mining software does create a valid comparison between the two. While the new higher hashrate }could{ be a fluke result, todays addition 24 more hours of data, along with multiple others reporting similar results, suggest it is not a fluke at all.
Perhaps you are using cards that Claymore doesnt give a benefit to? We dont know because nobody has compared the new improvement results across all gpu versions, other than we know 270s dont function well with it yet.
April 16, 2016, 04:13:10 PM
Tried DCR stratum on yiimp.ccminer.org:4252
One rejected share after each new job unit (((
Then all accepts till new job.
Update: not after each new job (rejected) ... need more testing ...
One rejected share after each new job unit (((
Then all accepts till new job.
Update: not after each new job (rejected) ... need more testing ...
It is called "stale shares".
For now (a short run) it has 145 total shares with 10 rejected. Rather bad statistics. Maybe the miner should stop working on old job immediately when the new job arrives?
It stops immediately, you can see that miner sends a share, then gets new job, then pool sends "rejected" answer. The problem is on pool - I see sometimes it takes pool about 3-5 seconds to send "accepted" response for share sent. If pool gets new block within this time it sends "rejected".
April 16, 2016, 04:09:18 PM
Tried DCR stratum on yiimp.ccminer.org:4252
One rejected share after each new job unit (((
Then all accepts till new job.
Update: not after each new job (rejected) ... need more testing ...
One rejected share after each new job unit (((
Then all accepts till new job.
Update: not after each new job (rejected) ... need more testing ...
It is called "stale shares".
For now (a short run) it has 145 total shares with 10 rejected. Rather bad statistics. Maybe the miner should stop working on old job immediately when the new job arrives?
April 16, 2016, 04:07:30 PM
check if the problem is gone.
Gone, many thanks Jump to: