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

[zureman90]

I don't know if this has anything to do with the pool or am I doing something wrong? started happening after the difficulty adjustment, hardly getting any shares through. "lost xx shares due to stratum disconnect on pool 0"

http://imageshack.com/a/img844/4828/l5sf.png

[1714704906]

1714704906

[1714704906]

1714704906

[oktay50000]

I might have to go back to directly mining dogecoins. I'm getting really really bad results the last 2 days.

im getting bad result
i put 13mh on this pool but last 2 days was getting 0.008 per mh which is very low
any suggestions?what is happening? all pools experiencing this?
now it looks like i mined doge(with droping btc price ) directly no diffrence

[Burgertm]

I think I'm going to switch pools until this stuff gets straightened out.  I'll be happy to come back once these issues are fixed.  My miner (1.2 Mh) was restarting because I wasn't getting accepted shares in 2 minutes.

[micro23]

I think I'm going to switch pools until this stuff gets straightened out.  I'll be happy to come back once these issues are fixed.  My miner (1.2 Mh) was restarting because I wasn't getting accepted shares in 2 minutes.

Yeah something is wrong I'm going to stick it out to help try and resolve the issues. At this point I'm loosing money mining tho... Loosing about $5 a day instead of $5 a day profit.

[azebro]

Something is wrong with stats. I've now put all worker names and on 10MH+ can see only 2mh (!!!)
Shall I remove the worker names?

i'm using BTC_workername

[oktay50000]

my hash droped from 13 to 5 mh 

[luthan]

maybe the pool should block the miner with 5Ghz.  seems like his arrival started causing more issues.

[oktay50000]

maybe the pool should block the miner with 5Ghz.  seems like his arrival started causing more issues.

+100000
i agree with that after that guy came in eveything torn apart

im switching to clever mine till waffle sort things up...
this is not good nor profitble pool until fix it once and for all

[azebro]

my hash droped from 13 to 5 mh 

Seems that BTC_worker is an issue.
Removed all worker names and stats are much higher now.

[evansearle42]

Oh no, what happen to this pool..

[resetgoris]

Today is a bad day to mine.

Ground is too damn sterile on waffle!

http://www.sydneyalternativemedia.com/blog/PreciousHoleInTheGround.JPG

[oktay50000]

Today is a bad day to mine.

Ground is too damn sterile on waffle!

lol

[richmke]

my suggestion, and probably the suggestion of A LOT of others, is to log the stat history so that we can get an accurate record without having to leave the page up all day.

1) I didn't want people to visit my stats once and then forget about it, meanwhile the stats continue to be downloaded. This was a waste not only for me storage wise, but for wafflepool and myself's network usage.

Maybe only log for 24 hours, and if the person has not checked in, then stop logging that address.

4) I figured that since people had their PC's on mining all the time anyways, if they wanted historical stats they could just keep the page open somewhere.

It does slightly lower the mining rate on the rig with the window open.

[richmke]

I will be bringing on a second rig, and added the "_worker" to my BTC address for the current worker.

Is there a way to get individual worker stats? I could not find the link.

[coyote]

maybe the pool should block the miner with 5Ghz.  seems like his arrival started causing more issues.

+100000
i agree with that after that guy came in eveything torn apart

im switching to clever mine till waffle sort things up...
this is not good nor profitble pool until fix it once and for all

OK - things have clearly gone a little wonky right now but I have faith in poolwaffle to sort it out. In fact I am prepared to bet his is flat out fire-fighting.

I am going to fail over to my backups as I can't sit & watch my rigs & stats 24/7, but I fully expect it to be temporary.

[phzi]

The big miner isn't the problem guys... The hashrate increase in general, maybe... but the whale only represents a portion of that - you may as well argue we should ban everyone who switched over from middlecoin.  At least the whale is probably using 1024 diff, instead of a ton of smaller miners hammering the servers.  I mean come on, think about it.

[amcdon]

The level of entitlement in this thread is pretty sad. This has been a bad week for all things crypto, just sit tight. You're welcome to go to another pool...hopefully that means you'll also stop posting here.

[zneww]

The level of entitlement in this thread is pretty sad. This has been a bad week for all things crypto, just sit tight. You're welcome to go to another pool...hopefully that means you'll also stop posting here.

It is not just here. Go to any other pool thread and its the same way. There is an outbreak of entitlement.

[poolwaffle]

Alright guys.

So I've been watching the impact of the bumped (hard-locked) difficulty of 512.  From my side, we're looking rediculously better.  All around load on servers is down by about 70% due to the adjustment.  This is from a few factors, first being we don't need to track every miner, and all of their previous shares (and times) for calculating and readjusting difficulty, second is the reduced amount of shares we have to log into the db (and then process into rounds, etc), third is the reduce in bandwidth required, which allows us more upstream bandwidth for outgoing block propagation.

All of these things combined makes for a _much_ better server-side.  From a miner standpoint, I can understand why it is a slight negative (smaller miners don't see shares nearly as often, may think something is broken).  But unless there is a major outcry about this, I think we need to stick with it.

The next thing is, we've boosted connectivity (a lot to do with bandwidth changes from difficulty), so we should be seeing fewer network-orphaned blocks, which is extremely good.  A bit of that was showing up earlier on the stats pages (from about 0.0080 --> 0.0086).

On top of that, I've just enabled ReddCoin, KarmaCoin, and PenguinCoin.  These are the first of their kind, in that we have to manually trade them (they're not on Cryptsy, where we auto-trade), and aren't listed on any exchanges that support API based trading.  What that means is two-fold:  1) Unexchanged balances will be significantly higher than normal (they wont move from unexchanged --> converted very often).  2) Unexchanged balance approximation will be off significantly more than it was previously, since we're exposed to market swings between the time they're earned, and the time they're converted (probably 2-3 times daily).  But even with the added risk, I think they should be more profitable on average.

Lastly, I've disabled a few more coins for the time being (under 15 difficulty), as when we switch to them, the block propagation time compared to block-find time is way too high, and results in us fighting ourselves for blocks (orphans).  As a simple example, say it takes about a full second for any block we find to make it around the world (propagate fully).  With coins under 15 difficulty, we have an average block time of about 7 seconds.  Meaning that 1/7th of the time, we might have already found a block, and not seen it yet (found at EU, hasn't gotten to USWest).  And we end up orphaning our own blocks about 1/7th of the time.

The long-term solution to this was discussed previously, which is to switch portions of our hashrate to lower difficulty blocks, in an attempt to keep our block-find time at a constant value (ex: never switch more power than would give us 20s block times).  But this is a reasonably large change to the profitability switcher, and the easier short-term solution is to just disable those coins until we can make those changes (a few days most likely).  So in the mean time we added additional coins (see above).

tldr; added new coins, disabled some coins, don't trust unexchanged balances

[qsrab]

too many coins disabled, payouts have been 0.005-0.008 per mhash after rejects/disconnects for the past 4 days mining 24/7. Pool was ruined when the botnet joined. To clevermining or hashcows?