[POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com - page 147.

cleanbaldy

newbie

Activity: 42

Merit: 0

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...

Secondary, something else changed last night at around 10:30, when the East server crashed for an hour? Still tweaking? The KHash issue did not get fixed, if that's what was going on...

http://i.imgur.com/ofjzQMk.jpg

ziddey

newbie

Activity: 16

Merit: 0

Quote from: poolwaffle on March 21, 2014, 12:42:28 PM

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

poolwaffle

sr. member

Activity: 322

Merit: 254

Quote from: gaalx on March 21, 2014, 12:19:30 PM

pw, mintcoin in coin balances - stuck? Thank you.

Please see any of the posts about this. Thank you.

gaalx

sr. member

Activity: 411

Merit: 250

pw, mintcoin in coin balances - stuck? Thank you.

poolwaffle

sr. member

Activity: 322

Merit: 254

API now includes stalerate, returned as a % of overall hashrate. Hashrate include stale hashrate.

For example, if your miner submitted 1MHs, of which half was rejected, "hashrate" would show 1000000, "stalerate" would show 50.00.

poolwaffle

sr. member

Activity: 322

Merit: 254

Quote from: xia0mingx on March 21, 2014, 10:26:03 AM

Quote from: poolwaffle on March 21, 2014, 10:02:29 AM

Quote from: xia0mingx on March 21, 2014, 09:59:00 AM

on the stats page, it says I have 3.5% stale rate but on my miner it says only 0.3% rejected. is there something else I need to put into account? thanks pw

This could be as simple as variance in shares/stales. If your 0.3% is over 24hrs, and just in the last 15min there was a burst, we'd be showing the burst, and yours wouldn't. Can you reset your stats locally, wait 15min and see how they line up?

Yup, you are right. 0.3% is over 24 hours. And the stale rate is now 0.00% on stats page. Thanks

Yep, could have been something as simple as us jumping on a small coin, and seeing a slightly higher reject rate during that time

\\

Quote from: Pfool on March 21, 2014, 10:27:38 AM

Is it possible to add the reject rate in the API ?

Yep, gimme a bit here

Pfool

full member

Activity: 217

Merit: 100

Quote from: poolwaffle on March 21, 2014, 09:55:35 AM

Quote from: xia0mingx on March 21, 2014, 09:52:12 AM

why is shift time reduced back to previous duration? Shocked

Duration wasn't changed, count was changed. It is just a matter of how we were keeping track of shares on the backend. This is mostly due to changes today for the following:

Worker stats are updated.
You should now see (on the stats page) your reject rate per worker, and stats coming from the stats page are now a ~15min average (instead of 5min average), in an attempt to have fewer people email me telling me their hashrate jumps around a lot.

Yeah !

Is it possible to add the reject rate in the API ?

Thank you

xia0mingx

newbie

Activity: 17

Merit: 0

Quote from: poolwaffle on March 21, 2014, 10:02:29 AM

Quote from: xia0mingx on March 21, 2014, 09:59:00 AM

on the stats page, it says I have 3.5% stale rate but on my miner it says only 0.3% rejected. is there something else I need to put into account? thanks pw

This could be as simple as variance in shares/stales. If your 0.3% is over 24hrs, and just in the last 15min there was a burst, we'd be showing the burst, and yours wouldn't. Can you reset your stats locally, wait 15min and see how they line up?

Yup, you are right. 0.3% is over 24 hours. And the stale rate is now 0.00% on stats page. Thanks

dexu

full member

Activity: 155

Merit: 100

STALE 0.00% good to know .. Wink

poolwaffle

sr. member

Activity: 322

Merit: 254

Quote from: xia0mingx on March 21, 2014, 09:59:00 AM

on the stats page, it says I have 3.5% stale rate but on my miner it says only 0.3% rejected. is there something else I need to put into account? thanks pw

This could be as simple as variance in shares/stales. If your 0.3% is over 24hrs, and just in the last 15min there was a burst, we'd be showing the burst, and yours wouldn't. Can you reset your stats locally, wait 15min and see how they line up?

MPBG

newbie

Activity: 1

Merit: 0

It's good to see your stales, I'm at 1.40%, which should be a little bit high I think, but it's fine.

xia0mingx

newbie

Activity: 17

Merit: 0

on the stats page, it says I have 3.5% stale rate but on my miner it says only 0.3% rejected. is there something else I need to put into account? thanks pw

poolwaffle

sr. member

Activity: 322

Merit: 254

Quote from: xia0mingx on March 21, 2014, 09:52:12 AM

why is shift time reduced back to previous duration? Shocked

Duration wasn't changed, count was changed. It is just a matter of how we were keeping track of shares on the backend. This is mostly due to changes today for the following:

Worker stats are updated.
You should now see (on the stats page) your reject rate per worker, and stats coming from the stats page are now a ~15min average (instead of 5min average), in an attempt to have fewer people email me telling me their hashrate jumps around a lot.

poolwaffle

sr. member

Activity: 322

Merit: 254

Quote from: tachyon_john on March 21, 2014, 09:50:55 AM

Quote from: tachyon_john on March 21, 2014, 09:47:46 AM

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...

xia0mingx

newbie

Activity: 17

Merit: 0

why is shift time reduced back to previous duration? Shocked

sorry for being noob for asking, but it doesnt affect my mining performance right? i only have a 1 MH/s rig. Sad

tachyon_john

newbie

Activity: 28

Merit: 0

Quote from: tachyon_john on March 21, 2014, 09:47:46 AM

Quote from: poolwaffle on March 21, 2014, 08:17:17 AM

Quote from: anon4250158 on March 21, 2014, 08:10:48 AM

I've been having the same issue as a few others since the new stratum server came online. As I write this, two of my 3 GPUs are idle while the third is hard at work. They idle for between 10 seconds and 5 minutes, which is ridiculous. What can I do to fix this?

My current CudaMiner command:

Code:

"C:\Miners\cudaminer.exe" -R 1 -C 1 -d 0 -a scrypt -o "stratum+tcp://uswest.wafflepool.com:3333" -u [address] -p x

I don't have much mining power (600kH/s) so I can't afford to have them idle for so long.

How exactly do you know they're idling?

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.

tachyon_john

newbie

Activity: 28

Merit: 0

Quote from: poolwaffle on March 21, 2014, 08:17:17 AM

Quote from: anon4250158 on March 21, 2014, 08:10:48 AM

I've been having the same issue as a few others since the new stratum server came online. As I write this, two of my 3 GPUs are idle while the third is hard at work. They idle for between 10 seconds and 5 minutes, which is ridiculous. What can I do to fix this?

My current CudaMiner command:

Code:

"C:\Miners\cudaminer.exe" -R 1 -C 1 -d 0 -a scrypt -o "stratum+tcp://uswest.wafflepool.com:3333" -u [address] -p x

I don't have much mining power (600kH/s) so I can't afford to have them idle for so long.

How exactly do you know they're idling?

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.

poolwaffle

sr. member

Activity: 322

Merit: 254

Quote from: ClemsonBTC on March 21, 2014, 09:26:48 AM

Quote from: suchmoon on March 21, 2014, 09:03:04 AM

Was useast down within the last 10-12 hours? I had my rigs mining to a backup pool for a while, not sure if there was something wrong on my end, or at waffle.

From around 3AM EST - 3:30AM EST wafflestats has my miners at 0Kh/s, so I assume so.

This is correct. USE crashed at about 3am, was down for a bit before I could get it back online.

dexu

full member

Activity: 155

Merit: 100

Quote from: Uniphase21 on March 21, 2014, 09:24:19 AM

Can anyone tell me if the KNC Titan script miner will work in wafflepool?

Yes, will work, when it be.

ClemsonBTC

newbie

Activity: 16

Merit: 0

Quote from: suchmoon on March 21, 2014, 09:03:04 AM

Was useast down within the last 10-12 hours? I had my rigs mining to a backup pool for a while, not sure if there was something wrong on my end, or at waffle.

From around 3AM EST - 3:30AM EST wafflestats has my miners at 0Kh/s, so I assume so.

Topic: [POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com - page 147. (Read 465769 times)