poolwaffle (OP)
|
|
March 21, 2014, 06:48:57 PM |
|
I have also observed the same behavior on 3 machines, and I have been collecting logs of GPU utilization through nvidia-smi which correlate to the cudaminer log I'm also keeping. I ran cudaminer with "-P" so I've also got a lot of the network protocol. I captured this happening probably ten times last night. It occurs on machines that are also connected to different stratum endpoints. So it's not just an issue with useast, or uswest, for example.
I should also add that the observed idle periods are occasionally quite long, often 15 to 20 seconds. This seems like a very long time to me. When it occurs, no timeouts or errors are printed by cudaminer, so from its point of view there is no problem. This behavior began when wafflepool switched to the new stratum code the other day. Prior to that, I never observed this behavior before. Any chance you have the protocol dump around when they're idling? Might let me know whats being sent/not being sent during that time... Yes, I have been logging both the protocol and the GPU utilization for the last 12 hours or so, so I should have several examples of where this occurs in my log. Right now I see it happening again at about 1:40pm central time...idle for about 1 minute and 45 seconds before it recovered. No errors from cudaminer when it happens, but no activity either. Same cudaminer binary worked fine for the last 2-3 weeks before the stratum change. I can send you a PM with a gzipped copy of the logs if you like. I sent you a short log snippet already last night, but sending the whole log may be more useful for you. If you can, email me the relevant part (maybe the last 3-4 messages from the server before idle, and the 3-4 messages when idling stops).
|
|
|
|
poolwaffle (OP)
|
|
March 21, 2014, 06:50:00 PM |
|
The problem is the high "vardiff" that causes small miners like gridseed and usb miners to show incorrect numbers. I mined on ghash.io while they had bonus, and because of the low difficulty, the khash on their website is much more stable on small units.
Are there any chance that wafflepool will get a lower vardiff than 512??
You just mean "diff", not "vardiff" Probably not. At least not in the immediate future. We did (just today) update the website to provide 15min hashrates instead of 5min, so your numbers should be _much_ closer to correct. As has been mentioned many times before, difficulty really doesn't affect anything other than variance.
|
|
|
|
gaalx
|
|
March 21, 2014, 06:50:30 PM Last edit: March 21, 2014, 07:03:45 PM by gaalx |
|
Please see any of the posts about this. Thank you.
BTC address I've been mining with is now invalid. Any way to move the balance to a different address? No longer have access to 1Hk2vF17rc2v7uoGLk4i25fr8wGemaGESH Thank you Nope. Won't move funds from one address to another unless you can sign a message with the first address. Its the only way for me to be sure you're not stealing someone else's coins. Sorry how to do it? now hidden rooms purses
|
|
|
|
tachyon_john
Newbie
Offline
Activity: 28
Merit: 0
|
|
March 21, 2014, 07:15:56 PM |
|
I have also observed the same behavior on 3 machines, and I have been collecting logs of GPU utilization through nvidia-smi which correlate to the cudaminer log I'm also keeping. I ran cudaminer with "-P" so I've also got a lot of the network protocol. I captured this happening probably ten times last night. It occurs on machines that are also connected to different stratum endpoints. So it's not just an issue with useast, or uswest, for example.
I should also add that the observed idle periods are occasionally quite long, often 15 to 20 seconds. This seems like a very long time to me. When it occurs, no timeouts or errors are printed by cudaminer, so from its point of view there is no problem. This behavior began when wafflepool switched to the new stratum code the other day. Prior to that, I never observed this behavior before. Any chance you have the protocol dump around when they're idling? Might let me know whats being sent/not being sent during that time... Yes, I have been logging both the protocol and the GPU utilization for the last 12 hours or so, so I should have several examples of where this occurs in my log. Right now I see it happening again at about 1:40pm central time...idle for about 1 minute and 45 seconds before it recovered. No errors from cudaminer when it happens, but no activity either. Same cudaminer binary worked fine for the last 2-3 weeks before the stratum change. I can send you a PM with a gzipped copy of the logs if you like. I sent you a short log snippet already last night, but sending the whole log may be more useful for you. If you can, email me the relevant part (maybe the last 3-4 messages from the server before idle, and the 3-4 messages when idling stops). Just sent you a relevant section of my log for one of these cases that occured at 13:40pm central time today. I can also send you full logs if that isn't enough. I emailed it to your gmail address.
|
|
|
|
cleanbaldy
Newbie
Offline
Activity: 42
Merit: 0
|
|
March 21, 2014, 07:19:40 PM |
|
Have we determined why Wafflepool isn't showing correct khash yet? Not only that, with the lower reported khash than before the server was changed, the payouts are not equal anymore. My BTC / Day / 1mH is LITERALLY going off of the falsely reported khash numbers. I'm losing out on 21% of my khash. That's HUGE. Something broke when you switched to the new server. Might want to take a look... I've had reports on my reddit post about this. Everyone is seeing it. Money = the reason we're here with you You've been amazing thus far. One or two days of tweaking and fixing a config is fine. If this continues, you may have people thinking you're stealing 20% of their money. Money makes people believe crazy things... Maybe I'm confused as to what you're showing in that graph... Nothing looks like the hashrate dropped by 20% anywhere in that graph... I posted the graph of the drop back on page 146 (This one, below), after I started noticing the issue. Immediately after the server reboot it happened. https://i.imgur.com/jX3dRRK.pngAnother user on Reddit, /u/codkill, posted this one: [–]codkill 2 points 16 hours ago*
I went from 6 MH/s to ~5 MH/s. My rejects have gone to almost 0%, which was great, until I noticed the loss of 18% of my total hashrate. I'm going to have to switch pools if this keeps up, which is too bad because Wafflepool has been the best I've used and really don't want to switch.https://i.imgur.com/cWwEjS2.jpg?1followed by my question "NVidia or AMD?" and he replied, [–]codkill 1 point 4 hours ago I'm actually running an even mix of all; AMD, NVidia, and CPUs. I have tried all of the other pools and always came back to Wafflepool, so I don't know what will happen if this keeps up. Then, another user, /u/LSSUDommo posted this: [–]LSSUDommo 2 points 18 hours ago
I'm having the same problem. My rig is running at a ~ 3.2 MH/s, but I'm being reported for only about 2.4. That's a 1/3rd of my production. I may have to move pools .
|
|
|
|
cleanbaldy
Newbie
Offline
Activity: 42
Merit: 0
|
|
March 21, 2014, 07:27:50 PM |
|
Hopefully this will help. It's a double whammy... Because the server is reporting wrong khash and the payments have gone down, we (everyone seeing this issue) are actually losing 25% of what we're doing somewhere.... HUGE deal... https://i.imgur.com/Ok6GHQH.png
|
|
|
|
phzi
|
|
March 21, 2014, 07:39:41 PM |
|
Hopefully this will help. It's a double whammy...
Because the server is reporting wrong khash and the payments have gone down, we (everyone seeing this issue) are actually losing 25% of what we're doing somewhere.... HUGE deal...
<snip>
Considering the minimum hashrate over the period you are viewing was 0MH/s, you average number is not going to be correct either. Server isn't reporting the wrong KH/s anywhere I have seen.
|
|
|
|
cleanbaldy
Newbie
Offline
Activity: 42
Merit: 0
|
|
March 21, 2014, 07:59:55 PM |
|
Hopefully this will help. It's a double whammy...
Because the server is reporting wrong khash and the payments have gone down, we (everyone seeing this issue) are actually losing 25% of what we're doing somewhere.... HUGE deal...
<snip>
Considering the minimum hashrate over the period you are viewing was 0MH/s, you average number is not going to be correct either. Server isn't reporting the wrong KH/s anywhere I have seen. That was due to the server outage for that hour. I could show you the last 6 hours and it's the same... down a large percentage. Good point though. It's still down and reporting incorrect the other 23 hours I have listed though. Do I REALLY have to wait another 24 hours to point out the fact that something is wrong with a new graph? haha.... I sure hope not.
|
|
|
|
MinerP
|
|
March 21, 2014, 08:07:40 PM |
|
Hopefully this will help. It's a double whammy...
Because the server is reporting wrong khash and the payments have gone down, we (everyone seeing this issue) are actually losing 25% of what we're doing somewhere.... HUGE deal...
<snip>
Considering the minimum hashrate over the period you are viewing was 0MH/s, you average number is not going to be correct either. Server isn't reporting the wrong KH/s anywhere I have seen. That minimum could be only be for a few minutes... I too am suffering at around 03:00AM-04:00AM pacific time two rigs always freeze ever since update. Not sure is this is due to server resets and my rigs not being able to recover or just coincidence. I am sleeping at this hour so i dont find out till i wake up.
|
|
|
|
phzi
|
|
March 21, 2014, 08:13:57 PM |
|
Good point though. It's still down and reporting incorrect the other 23 hours I have listed though.
Do I REALLY have to wait another 24 hours to point out the fact that something is wrong with a new graph? haha.... I sure hope not.
I tend to avoid measuring performance until several days have passed. That said - my average hashrate looks fine. I am losing shares to reject rate and losing a few KH/s due to the need to re-tune my miners, but WafflePool's displayed rates look quite accurate compared to accepted WU. As I have said before, I did prefer when WP accepted 1-block-late shares. However, mining profits per card are still looking decent right now given current market conditions, and the new stratum layer does seem pretty effective so far. I too am suffering at around 03:00AM-04:00AM pacific time two rigs always freeze ever since update. Not sure is this is due to server resets and my rigs not being able to recover or just coincidence. I am sleeping at this hour so i dont find out till i wake up.
Hm, does look like I have a noticeable dip in accepted shares around 4am across 5 miners. No crashes tho. Will watch to see if this behavior is repeated.
|
|
|
|
oktay50000
|
|
March 21, 2014, 08:19:04 PM |
|
yes ive noticed that hash drop too im putting 13.5 mh on waffle but graphs showings showing only 11.3~12 mh
|
BTC : bc1qqz9hvv806w2zs42mx4rn576whxmr202yxp00e9
feel free to buy me a bear
|
|
|
poolwaffle (OP)
|
|
March 21, 2014, 08:20:48 PM |
|
Cleanbaldy, any chance you could email me your address so I can take a look closer at your stats. I see what you're talking about, and I'm trying to figure out what could cause it.
Information that would be useful: - cgminer (or whatever) params - endpoint you're connected to - address
Also, if possible, two other pieces of info that would be awesome: - what happens if you switch to a different endpoint (wait 15min for stats to push through completely) - restart miner to a different address that you own, wait for 5min and kill it, note how many shares/rejects it said, check the stats on wp and see if they match up
|
|
|
|
comeonalready
|
|
March 21, 2014, 08:29:26 PM |
|
Good point though. It's still down and reporting incorrect the other 23 hours I have listed though.
Do I REALLY have to wait another 24 hours to point out the fact that something is wrong with a new graph? haha.... I sure hope not.
I tend to avoid measuring performance until several days have passed. That said - my average hashrate looks fine. I am losing shares to reject rate and losing a few KH/s due to the need to re-tune my miners, but WafflePool's displayed rates look quite accurate compared to accepted WU. As I have said before, I did prefer when WP accepted 1-block-late shares. However, mining profits per card are still looking decent right now given current market conditions, and the new stratum layer does seem pretty effective so far. I too am suffering at around 03:00AM-04:00AM pacific time two rigs always freeze ever since update. Not sure is this is due to server resets and my rigs not being able to recover or just coincidence. I am sleeping at this hour so i dont find out till i wake up.
Hm, does look like I have a noticeable dip in accepted shares around 4am across 5 miners. No crashes tho. Will watch to see if this behavior is repeated. My logs show that us-east server was down from 2:45ish to 4:18ish EST. If you didn't fail over to another server, then your daily stats for today will drop by approximately 6.5% (assuming no further outages)
|
|
|
|
JHammer
Member
Offline
Activity: 112
Merit: 10
|
|
March 21, 2014, 08:52:29 PM |
|
New here so hopefully not a silly question but is WU not the most accurate thing to look at to determine your true Hash speed with the pool you are on?
I noticed before the server upgrade my WU was steady at 2,250 and now its been steady at 1,965. Maybe since the server upgrade I need to tweak my Config? Just not really sure what to tweak.. And I use to get zero rejects now I have like 2.35%(Which I assume is not bad)
Thanks!
|
|
|
|
Thirtybird
|
|
March 21, 2014, 09:01:22 PM |
|
New here so hopefully not a silly question but is WU not the most accurate thing to look at to determine your true Hash speed with the pool you are on?
I noticed before the server upgrade my WU was steady at 2,250 and now its been steady at 1,965. Maybe since the server upgrade I need to tweak my Config? Just not really sure what to tweak.. And I use to get zero rejects now I have like 2.35%(Which I assume is not bad)
Thanks!
Yes and no - It should be close. W/U is the ratio of Difficulty 1 hashes per minute you've solved. If your miner supports U (utility), that is the difficulty of shares you've had accepted BY THE POOL per minute. W/U doesn't take pool submission into account. My 78500 for instance has: 354 KH/sec WU : 334.38/m U : 332.57/m If you get a lot of rejects, or are having HW errors, you will see a much larger disparity between the two values. I've got few rejects (20 in 4 days) and no HW errors, so they're real close.
|
|
|
|
GalacticMiningCorp
Newbie
Offline
Activity: 31
Merit: 0
|
|
March 21, 2014, 09:04:18 PM |
|
New here so hopefully not a silly question but is WU not the most accurate thing to look at to determine your true Hash speed with the pool you are on?
As far as I've been able to determine, Work Utility is the be-all and end-all to how effectively you're mining. It's essentially the end result of everything like rejects, luck in finding blocks, etc. I tune to have the highest possible WU, even over hash rate. From what I've read in cgminer's docs, a WU ratio of around 0.92 (in relation to kh/s) is ideal; I'm not sure if this is still accurate though. Edit: WU is a stat that is slow to build over time. Not something where you change a parameter, watch it for 30 seconds and change again. It can take hours if not days to give a solid estimate.
|
|
|
|
JHammer
Member
Offline
Activity: 112
Merit: 10
|
|
March 21, 2014, 09:33:40 PM |
|
Thanks Guys for your quick Replies..
|
|
|
|
fabrizziop
|
|
March 21, 2014, 09:37:15 PM |
|
I'm getting TONS of duplicate shares. What's the cause?, I didn't see that on other pools.
|
|
|
|
vals
Newbie
Offline
Activity: 9
Merit: 0
|
|
March 21, 2014, 10:16:07 PM |
|
|
|
|
|
haggis
|
|
March 21, 2014, 10:27:09 PM |
|
|
|
|
|
|