Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 80. (Read 6590565 times)
September 29, 2019, 12:20:48 PM
I am having internet connection issues while mining. I checked some articles and tried the solution they offered but they didn't seem to be working for me. I tried a different source of internet and still, it doesn't work. The problem is, when I start to mine with my GPU, in 10 minutes, I lost the wi-fi connection. The modem is close to me, I haven't get the chance to use a cable but I don't think it will work. What is causing these problems?
September 29, 2019, 06:58:34 AM
I know you can take a log file and if you have a long enough mining duration say 1 month, then you can easily add all the accepted+rejected+stale and get an accurate measurement and being within +- 1% is fairly close.
I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
Nobody is talking about speed fluctuations here. The averaged stated speed incorporates them. If miner does not work at some moment it prints 0.000 Mh/s in console (and log) and this zero is heaped when calculating the averaged speed and the number of samples is increased by one for this zero. Come on man use a little the last floor of your body. I talk that this averaged stated speed in console and in the log is 1.5% higher than the real one which can be calculated from the found shares (locally, not at the pools side), difficulty and the time that the miner has worked.I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
I'm trying to follow but it's a bit confusing. So now you are claiming that the speed that the miner displays in console and reports to the pool is 1.5% higher than the actual one? and is that somehow related to your previous claim of Claymore taking higher than advertised devfee?
If you are into this kind of action can you maybe do all of us a favor and perform the same analysis on this one https://bitcointalksearch.org/topic/phoenixminer-62c-fastest-ethereumethash-miner-with-lowest-devfee-winlinux-2647654
And maybe post here with numbers and such?
I know for myself I'd be very much interested to see the actual numbers. Thx.
September 29, 2019, 06:12:46 AM
I know you can take a log file and if you have a long enough mining duration say 1 month, then you can easily add all the accepted+rejected+stale and get an accurate measurement and being within +- 1% is fairly close.
I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
Nobody is talking about speed fluctuations here. The averaged stated speed incorporates them. If miner does not work at some moment it prints 0.000 Mh/s in console (and log) and this zero is heaped when calculating the averaged speed and the number of samples is increased by one for this zero. Come on man use a little the last floor of your body. I talk that this averaged stated speed in console and in the log is 1.5% higher than the real one which can be calculated from the found shares (locally, not at the pools side), difficulty and the time that the miner has worked.I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
I'm trying to follow but it's a bit confusing. So now you are claiming that the speed that the miner displays in console and reports to the pool is 1.5% higher than the actual one? and is that somehow related to your previous claim of Claymore taking higher than advertised devfee?
If you are into this kind of action can you maybe do all of us a favor and perform the same analysis on this one https://bitcointalksearch.org/topic/phoenixminer-62c-fastest-ethereumethash-miner-with-lowest-devfee-winlinux-2647654
And maybe post here with numbers and such?
I know for myself I'd be very much interested to see the actual numbers. Thx.
September 29, 2019, 05:01:13 AM
I know you can take a log file and if you have a long enough mining duration say 1 month, then you can easily add all the accepted+rejected+stale and get an accurate measurement and being within +- 1% is fairly close.
I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
Nobody is talking about speed fluctuations here. The averaged stated speed incorporates them. If miner does not work at some moment it prints 0.000 Mh/s in console (and log) and this zero is heaped when calculating the averaged speed and the number of samples is increased by one for this zero. Come on man use a little the last floor of your body. I talk that this averaged stated speed in console and in the log is 1.5% higher than the real one which can be calculated from the found shares (locally, not at the pools side), difficulty and the time that the miner has worked.I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
I'm trying to follow but it's a bit confusing. So now you are claiming that the speed that the miner displays in console and reports to the pool is 1.5% higher than the actual one? and is that somehow related to your previous claim of Claymore taking higher than advertised devfee?
September 29, 2019, 04:53:46 AM
Did anyone succeeded in improving 1060 hashrate with any of v15 tighter straps and what's the rate/GPU?
This how it's most stable on phoenix for me:
Using strap 2 I'm able to see them doing over 26MH, but hashrate jumps around and eventually stabilizes around the same level.
This how it's most stable on phoenix for me:
Using strap 2 I'm able to see them doing over 26MH, but hashrate jumps around and eventually stabilizes around the same level.
September 29, 2019, 04:44:42 AM
I know you can take a log file and if you have a long enough mining duration say 1 month, then you can easily add all the accepted+rejected+stale and get an accurate measurement and being within +- 1% is fairly close.
I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
Nobody is talking about speed fluctuations here. The averaged stated speed incorporates them. If miner does not work at some moment it prints 0.000 Mh/s in console (and log) and this zero is heaped when calculating the averaged speed and the number of samples is increased by one for this zero. Come on man use a little the last floor of your body. I talk that this averaged stated speed in console and in the log is 1.5% higher than the real one which can be calculated from the found shares (locally, not at the pools side), difficulty and the time that the miner has worked.I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
I'm trying to follow but it's a bit confusing. So now you are claiming that the speed that the miner displays in console and reports to the pool is 1.5% higher than the actual one? and is that somehow related to your previous claim of Claymore taking higher than advertised devfee?
September 29, 2019, 03:19:12 AM
I know you can take a log file and if you have a long enough mining duration say 1 month, then you can easily add all the accepted+rejected+stale and get an accurate measurement and being within +- 1% is fairly close.
I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
Nobody is talking about speed fluctuations here. The averaged stated speed incorporates them. If miner does not work at some moment it prints 0.000 Mh/s in console (and log) and this zero is heaped when calculating the averaged speed and the number of samples is increased by one for this zero. Come on man use a little the last floor of your body. I talk that this averaged stated speed in console and in the log is 1.5% higher than the real one which can be calculated from the found shares (locally, not at the pools side), difficulty and the time that the miner has worked. I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
September 29, 2019, 01:41:34 AM
I know you can take a log file and if you have a long enough mining duration say 1 month, then you can easily add all the accepted+rejected+stale and get an accurate measurement and being within +- 1% is fairly close.
I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
I think the 1% loss you are talking about is not related to the Claymore software but most likely due to the GPU drivers. I know with my AMD RX series GPUs there is a time when some GPUs hash a little slower for a few seconds and then resume the optimal speed. Been trying to figure out why it happens but couldn't and just left it the way it was because the speed loss was minimal. So find in your logs if your speed was always constant or did it slow down from time to time. You can probably find this easily with MS Excel when you load your log file.
September 28, 2019, 05:21:50 PM
I don't mind the honestly won millions but
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind.
But if you call me a thief and state that I lie about devfee rate, show some proofs.
So you were talking about fake devfee rate 1.3%, now it's fine but there is fake hashrate 1.5%, right? Where do you take these numbers? Ok, probably you have own good source of them.
From my experience, I always see a couple of percents fluctuations in hashrate on pool side, and usually it's a bit less than miner shows because miner shows raw hashrate, i.e. it ignores devfee, stale and invalid shares, startup time, dag creation file and other minor things. But pool has to calculate miner's speed from shares only so there is some small error rate there, always. And hashrate that you see on the pool is "final" hashrate, it's always a bit lower.
Anyway, if you don't like hashrate that you see, or don't believe it - just use some other miner that shows better numbers or numbers that you believe. I even saw reports like "I tried miner X and now I see +10% shares on pool", so some people think that they get a lot more than 1.5% after changing miner
You can try this way too and find the best miner for you, no one forces you to use my miner if you don't like it.PS. I assume that you don't use "devfee cut" tools or cracks, in this case miner really may show some fake hashrate, read Readme for details.
You are correct, everybody can examine the logfile and find some better miner if don't like the results.
As easy as pie.
September 28, 2019, 05:13:51 PM
I don't mind the honestly won millions but
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind.
But if you call me a thief and state that I lie about devfee rate, show some proofs.
So you were talking about fake devfee rate 1.3%, now it's fine but there is fake hashrate 1.5%, right? Where do you take these numbers? Ok, probably you have own good source of them.
From my experience, I always see a couple of percents fluctuations in hashrate on pool side, and usually it's a bit less than miner shows because miner shows raw hashrate, i.e. it ignores devfee, stale and invalid shares, startup time, dag creation file and other minor things. But pool has to calculate miner's speed from shares only so there is some small error rate there, always. And hashrate that you see on the pool is "final" hashrate, it's always a bit lower.
Anyway, if you don't like hashrate that you see, or don't believe it - just use some other miner that shows better numbers or numbers that you believe. I even saw reports like "I tried miner X and now I see +10% shares on pool", so some people think that they get a lot more than 1.5% after changing miner
You can try this way too and find the best miner for you, no one forces you to use my miner if you don't like it.PS. I assume that you don't use "devfee cut" tools or cracks, in this case miner really may show some fake hashrate, read Readme for details.
You are correct, everybody can examine the logfile and find some better miner if don't like the results.
As easy as pie.
September 28, 2019, 04:47:20 PM
I don't mind the honestly won millions but
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind.
But if you call me a thief and state that I lie about devfee rate, show some proofs.
So you were talking about fake devfee rate 1.3%, now it's fine but there is fake hashrate 1.5%, right? Where do you take these numbers? Ok, probably you have own good source of them.
From my experience, I always see a couple of percents fluctuations in hashrate on pool side, and usually it's a bit less than miner shows because miner shows raw hashrate, i.e. it ignores devfee, stale and invalid shares, startup time, dag creation file and other minor things. But pool has to calculate miner's speed from shares only so there is some small error rate there, always. And hashrate that you see on the pool is "final" hashrate, it's always a bit lower.
Anyway, if you don't like hashrate that you see, or don't believe it - just use some other miner that shows better numbers or numbers that you believe. I even saw reports like "I tried miner X and now I see +10% shares on pool", so some people think that they get a lot more than 1.5% after changing miner
You can try this way too and find the best miner for you, no one forces you to use my miner if you don't like it.PS. I assume that you don't use "devfee cut" tools or cracks, in this case miner really may show some fake hashrate, read Readme for details.
September 28, 2019, 03:59:31 PM
Hey Claymore
Cannot resolve 'eu1.ethermine.org'
ETH: Stratum - Cannot connect to eu1.ethermine.org:5555
DevFee: ETH: Stratum - Failed to connect, retry in 20 sec...
my settings are correct and I am mining normally. But your devfee settings are not working and the mining doesn't continue if this is not fixed. Such a great problem. I kept getting this error many times and I lost bunch of times. Tell me what to do if I wasn't controling my screens? I was gonna lose a night maybe?
Cannot resolve 'eu1.ethermine.org'
ETH: Stratum - Cannot connect to eu1.ethermine.org:5555
DevFee: ETH: Stratum - Failed to connect, retry in 20 sec...
my settings are correct and I am mining normally. But your devfee settings are not working and the mining doesn't continue if this is not fixed. Such a great problem. I kept getting this error many times and I lost bunch of times. Tell me what to do if I wasn't controling my screens? I was gonna lose a night maybe?
September 28, 2019, 01:40:22 PM
I don't mind the honestly won millions but
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind.
But if you call me a thief and state that I lie about devfee rate, show some proofs.
So you were talking about fake devfee rate 1.3%, now it's fine but there is fake hashrate 1.5%, right? Where do you take these numbers? Ok, probably you have own good source of them.
From my experience, I always see a couple of percents fluctuations in hashrate on pool side, and usually it's a bit less than miner shows because miner shows raw hashrate, i.e. it ignores devfee, stale and invalid shares, startup time, dag creation file and other minor things. But pool has to calculate miner's speed from shares only so there is some small error rate there, always. And hashrate that you see on the pool is "final" hashrate, it's always a bit lower.
Anyway, if you don't like hashrate that you see, or don't believe it - just use some other miner that shows better numbers or numbers that you believe. I even saw reports like "I tried miner X and now I see +10% shares on pool", so some people think that they get a lot more than 1.5% after changing miner
You can try this way too and find the best miner for you, no one forces you to use my miner if you don't like it.PS. I assume that you don't use "devfee cut" tools or cracks, in this case miner really may show some fake hashrate, read Readme for details.
September 28, 2019, 01:05:55 PM
I am using RX580 and started to mine a week ago. The supposed hash rate should be 30-31 mh I guess but I don't seem to get that one. I only get 27.7 mh. I made lots of searches, used the latest drivers and switched my gpu to compute mode, nothing changed. Any other advices that I can get?
What clocks are you running?
well, I tried different time periods if you mean this. Night or day, doesn't matter. It is stable around 27.7 ish. And another issues that I have is internet connection. I lose the internet connection if I try to use the internet for other things with mining. I don't have a rig, I am just learning and trying through my personal computer.
The frequencies of your GPU and Vram.
I get 33,1 Mh/s (RX580) with these settings :
-rxboost 1 -strap 2 -cclock 1220 -mclock 2200 -cvddc 900
I used your setting and got 31 Mh/s, thanks. What about the internet connection issues that I get? Could it be related to my modem? Another question is what do you mine and what is your ROI?
Are you using unmodified GPU? I mean you didn't actually do a BIOS mod? That's really interesting if its the case.
You should not stop there. A 580 should be able to go above 32MH. Also try lowering the voltage to around 850 and lowering the core clock and maxing out the mem clock
September 28, 2019, 12:56:58 PM
I don't mind the honestly won millions but
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind.
But if you call me a thief and state that I lie about devfee rate, show some proofs.
that's funny:) are you being serious? without even taking into account possible network issues, possible stale shares, and whatever else. why would you assume that the pool that you are using is not stealing you hash, but Claymore does?
btw does it have any advantages over using phoenix miner(with lower fee) along with amdmemtweak?
or does this miner is actually able to produce same hash rate as the bios modded cards?
September 28, 2019, 12:34:04 PM
I am using RX580 and started to mine a week ago. The supposed hash rate should be 30-31 mh I guess but I don't seem to get that one. I only get 27.7 mh. I made lots of searches, used the latest drivers and switched my gpu to compute mode, nothing changed. Any other advices that I can get?
What clocks are you running?
well, I tried different time periods if you mean this. Night or day, doesn't matter. It is stable around 27.7 ish. And another issues that I have is internet connection. I lose the internet connection if I try to use the internet for other things with mining. I don't have a rig, I am just learning and trying through my personal computer.
The frequencies of your GPU and Vram.
I get 33,1 Mh/s (RX580) with these settings :
-rxboost 1 -strap 2 -cclock 1220 -mclock 2200 -cvddc 900
I used your setting and got 31 Mh/s, thanks. What about the internet connection issues that I get? Could it be related to my modem? Another question is what do you mine and what is your ROI?
September 28, 2019, 12:05:28 PM
I don't mind the honestly won millions but
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind.
But if you call me a thief and state that I lie about devfee rate, show some proofs.
September 28, 2019, 11:31:35 AM
I am using RX580 and started to mine a week ago. The supposed hash rate should be 30-31 mh I guess but I don't seem to get that one. I only get 27.7 mh. I made lots of searches, used the latest drivers and switched my gpu to compute mode, nothing changed. Any other advices that I can get?
What clocks are you running?
well, I tried different time periods if you mean this. Night or day, doesn't matter. It is stable around 27.7 ish. And another issues that I have is internet connection. I lose the internet connection if I try to use the internet for other things with mining. I don't have a rig, I am just learning and trying through my personal computer.
The frequencies of your GPU and Vram.
I get 33,1 Mh/s (RX580) with these settings :
-rxboost 1 -strap 2 -cclock 1220 -mclock 2200 -cvddc 900
September 28, 2019, 10:58:08 AM
I am using RX580 and started to mine a week ago. The supposed hash rate should be 30-31 mh I guess but I don't seem to get that one. I only get 27.7 mh. I made lots of searches, used the latest drivers and switched my gpu to compute mode, nothing changed. Any other advices that I can get?
What clocks are you running?
well, I tried different time periods if you mean this. Night or day, doesn't matter. It is stable around 27.7 ish. And another issues that I have is internet connection. I lose the internet connection if I try to use the internet for other things with mining. I don't have a rig, I am just learning and trying through my personal computer.
September 28, 2019, 10:45:59 AM
@big_daddy: thanks!
Unfortunately, pools don't send block number, they only send seedhash so miner can detect epoch number only, not the block number.
Is it possible to add the block number each time this line appears ?
Unfortunately, pools don't send block number, they only send seedhash so miner can detect epoch number only, not the block number.
Jump to: