With v.4.0 DAG creation is fast and stable, well done! same speed for me, is a real gain using -ethi 8?
I'm using -ethi 16 and it improves my speed a little bit
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1351. (Read 6590565 times)
April 27, 2016, 06:34:37 PM
With v.4.0 DAG creation is fast and stable, well done! same speed for me, is a real gain using -ethi 8?
I'm using -ethi 16 and it improves my speed a little bit
April 27, 2016, 06:32:25 PM
With v.4.0 DAG creation is fast and stable, well done! same speed for me, is a real gain using -ethi 8?
April 27, 2016, 06:27:23 PM
p.s. I think you should stop releasing updates the day after new epoch dag, people cant remember they are loosing performance on most of the cards with every new dag 
@ claymore
what about chunking the dagger file, is there any chance that it would reduce tlb trashing?
April 27, 2016, 06:25:07 PM
look something crazy!
BitClub Mines Block 409008 and Gets a $136,000 Fee
http://bitcoinist.net/bitclub-network-mines-colossal-fee/
BitClub Mines Block 409008 and Gets a $136,000 Fee
http://bitcoinist.net/bitclub-network-mines-colossal-fee/
And what does this have to do with the miner and ETH?. Nothing. So post this elsewhere wayyyy off topic.
relax, its just a timeout...
April 27, 2016, 06:18:10 PM
@Claymore in my command line i use ethermine with eth-proxy:
Because there is no way to check if my failover is set properly does it suppose to look like that:
or should i put the name of the worker after the wallet separated wit dot?
Code:
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0x8d5ad572f59fbc5bb********266d3083ea9290.RigName -epsw x -esm 0 -mode 1 -wd 1 -r 1 -dbg -1 -etha 1
Because there is no way to check if my failover is set properly does it suppose to look like that:
Code:
POOL: us1.ethermine.org:4444, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0
POOL: eth-eu.dwarfpool.com:8008, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0
or should i put the name of the worker after the wallet separated wit dot?
I'd recommend:
POOL: us1.ethermine.org:4444, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290.RigName, PSW: x, ESM: 1
Thanks, i will do that but probably keep esm:0 maybe just feeling but i think i got better hashrate on the pool with eth-proxy than the qtminer mode.
p.s. I think you should stop releasing updates the day after new epoch dag, people cant remember they are loosing performance on most of the cards with every new dag
April 27, 2016, 05:50:43 PM
@Claymore in my command line i use ethermine with eth-proxy:
Because there is no way to check if my failover is set properly does it suppose to look like that:
or should i put the name of the worker after the wallet separated wit dot?
Code:
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0x8d5ad572f59fbc5bb********266d3083ea9290.RigName -epsw x -esm 0 -mode 1 -wd 1 -r 1 -dbg -1 -etha 1
Because there is no way to check if my failover is set properly does it suppose to look like that:
Code:
POOL: us1.ethermine.org:4444, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0
POOL: eth-eu.dwarfpool.com:8008, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0
or should i put the name of the worker after the wallet separated wit dot?
I'd recommend:
POOL: us1.ethermine.org:4444, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290.RigName, PSW: x, ESM: 1
April 27, 2016, 05:46:01 PM
@Claymore in my command line i use ethermine with eth-proxy:
Because there is no way to check if my failover is set properly does it suppose to look like that:
or should i put the name of the worker after the wallet separated wit dot?
Code:
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0x8d5ad572f59fbc5bb********266d3083ea9290.RigName -epsw x -esm 0 -mode 1 -wd 1 -r 1 -dbg -1 -etha 1
Because there is no way to check if my failover is set properly does it suppose to look like that:
Code:
POOL: us1.ethermine.org:4444, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0
POOL: eth-eu.dwarfpool.com:8008, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0
or should i put the name of the worker after the wallet separated wit dot?
Unplug your net for a few seconds and it should fail.
April 27, 2016, 05:42:03 PM
If you are still sure that v4.0 is slower with "-ethi 16" option on epoch #47 than previous versions on same epoch - PM me logs for both versions so I can check the reason.
v4 is working flawlessly on my rigs and on my PC
April 27, 2016, 05:34:45 PM
on my 270 rigs i get slower hrate
v3.2 ~ 57.2
v4.0 with ethi 16 ~ 55.9
cards are 5-10c hotter that on v3.2
will test it on 380
edit: on 380 everything is ok
v3.2 ~ 57.2
v4.0 with ethi 16 ~ 55.9
cards are 5-10c hotter that on v3.2
will test it on 380
edit: on 380 everything is ok
At this moment I have a few reports about slower hashrate. And after checking all they are not true.
Two reports were about previous epoch #46 for v3.2 and epoch #47 for v4.0, that's the reason.
Two reports were about "-ethi 8" that is used in 3.3 and v4.0 that uses "-ethi 8" by default.
And one report was related to both reasons at once
If you are still sure that v4.0 is slower with "-ethi 16" option on epoch #47 than previous versions on same epoch - PM me logs for both versions so I can check the reason.
April 27, 2016, 05:22:26 PM
on my 270 rigs i get slower hrate
v3.2 ~ 57.2
v4.0 with ethi 16 ~ 55.9
cards are 5-10c hotter that on v3.2
will test it on 380
edit: on 380 everything is ok
v3.2 ~ 57.2
v4.0 with ethi 16 ~ 55.9
cards are 5-10c hotter that on v3.2
will test it on 380
edit: on 380 everything is ok
April 27, 2016, 05:22:14 PM
look something crazy!
BitClub Mines Block 409008 and Gets a $136,000 Fee
http://bitcoinist.net/bitclub-network-mines-colossal-fee/
BitClub Mines Block 409008 and Gets a $136,000 Fee
http://bitcoinist.net/bitclub-network-mines-colossal-fee/
And what does this have to do with the miner and ETH?. Nothing. So post this elsewhere wayyyy off topic.
April 27, 2016, 05:02:28 PM
look something crazy!
BitClub Mines Block 409008 and Gets a $136,000 Fee
http://bitcoinist.net/bitclub-network-mines-colossal-fee/
BitClub Mines Block 409008 and Gets a $136,000 Fee
http://bitcoinist.net/bitclub-network-mines-colossal-fee/
April 27, 2016, 04:57:47 PM
Fairly interesting to see this mining with ETH-only produces a higher rate than using eth miner even with 1% fee taken out is a big improvement.
Not sure how you guys tweekd or what tweed and improved on it but ya done something so my 1% is welcomed.
Only thing I do notice a drop on is earnings when dual mining is on with decred and see a 20 to 30% drop in hash on pool and get a fair few rejected shares on Decred too. Mining goes to about 50MH out of 60MH using R9 x280x gpus and tried changing settings but makes no odds most I managed to cut it down to is 20 to 25%. Any advise on how can improve this. Thinking to just mine ETH mode only.
Not sure how you guys tweekd or what tweed and improved on it but ya done something so my 1% is welcomed.
Only thing I do notice a drop on is earnings when dual mining is on with decred and see a 20 to 30% drop in hash on pool and get a fair few rejected shares on Decred too. Mining goes to about 50MH out of 60MH using R9 x280x gpus and tried changing settings but makes no odds most I managed to cut it down to is 20 to 25%. Any advise on how can improve this. Thinking to just mine ETH mode only.
April 27, 2016, 04:52:36 PM
Good job! Waiting for proxy & webstats/monitor!
April 27, 2016, 04:39:39 PM
Thank God - no DAG files anymore.
the best thing u ever did Claymore.
Thank you.
the best thing u ever did Claymore.
Thank you.
April 27, 2016, 04:32:30 PM
4.0 installed and working great. Only .5 MH less on the speed.
It must have same speed.
If you are sure that v3.3 works faster for current epoch #47 - PM me the log files for both v4.0 and v3.3 so I can check it.
I was still on 3.2, never upgraded to 3.3
v3.2 uses "-ethi 16" by default, v3.3 and v4.0 use "-ethi 8" by default, so add "-ethi 16" to command line to use same settings. If you still have different speeds with "-ethi 16", PM logs for both versions.
That did it
April 27, 2016, 04:00:11 PM
After six hours. Still working rock solid, in the cold systems room.
Many thanks Trimegistus...
Good news! You're welcome
April 27, 2016, 03:51:12 PM
4.0 installed and working great. Only .5 MH less on the speed.
It must have same speed.
If you are sure that v3.3 works faster for current epoch #47 - PM me the log files for both v4.0 and v3.3 so I can check it.
I was still on 3.2, never upgraded to 3.3
v3.2 uses "-ethi 16" by default, v3.3 and v4.0 use "-ethi 8" by default, so add "-ethi 16" to command line to use same settings. If you still have different speeds with "-ethi 16", PM logs for both versions.
April 27, 2016, 03:47:57 PM
4.0 installed and working great. Only .5 MH less on the speed.
It must have same speed.
If you are sure that v3.3 works faster for current epoch #47 - PM me the log files for both v4.0 and v3.3 so I can check it.
I was still on 3.2, never upgraded to 3.3
April 27, 2016, 03:42:38 PM
4.0 installed and working great. Only .5 MH less on the speed.
It must have same speed.
If you are sure that v3.3 works faster for current epoch #47 - PM me the log files for both v4.0 and v3.3 so I can check it.
Jump to: