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

Hey my new bros n Sis's, just a quik question
\

What time of day is waffle pay time to your BTC address   - Midddlecoin used to b around 2am ust

The issue is just the overhead of managing individual workers separately.  Each endpoint (usw, use, eu) is currenly comprised of 4 physical servers each (12 total servers).  Previously we were switching a single server at a time (based on hashrate for that server), but at this point, even a single server is too much (assume 800MH/s per server - even though theres some variance).  The simple solution (although much more expensive) is to have 10 physical servers instead of 4 at each endpoint, essentially just subdividing a bit further, but this fails as well at some arbitrary time in the future, and really isn't an acceptable solution (I'd rather have something good, rather than taped together with a "well this will push the problem off til later").

But the first piece here is to figure out how much it will actually matter.  I don't think for smaller coins we want to aim for anything faster than 1/2 their average block time (for this excersize, lets go with aiming for 30 seconds), or else we're just wrecking the coin too quickly.  Hashrate also really doesn't matter that much, as the variance when dealing with a small portion of our pool isn't an issue.

And while typing out this reply, and trying to get hard data to paste, I think I've convinced myself
Here is a quick list of the coins we currently support, that are under 10 difficulty (mining-disabled currently), their difficulty, and the hashrate required to have an average block speed of 30 seconds.
name - diff: hashrate for 30s blocktime
digitalcoin - 9.04891019: 1.30 GH/s
philosopherstone - 8.56102751: 1.23 GH/s
luckycoin - 8.36572523: 1.20 GH/s
mincoin - 6.06047996: 867.65 MH/s
spots - 4.3518826: 623.04 MH/s
chncoin - 3.14754512: 450.62 MH/s
elacoin - 3.05901337: 437.95 MH/s
casinocoin - 2.81701341: 403.30 MH/s
cosmoscoin - 2.50721665: 358.95 MH/s
grandcoin - 2.18049873: 312.17 MH/s
franko - 1.79813971: 257.43 MH/s
diamond - 1.65509142: 236.95 MH/s
phoenixcoin - 1.56782297: 224.46 MH/s
stablecoin - 1.54614731: 221.36 MH/s
alphacoin - 0.84637737: 121.17 MH/s
bottlecaps - 0.67486716: 96.62 MH/s

As you can see, for the vast majority of these, we'd be needing to switch less than 1GHs (most less than 500MHs), 5-10% of the pool at current size.

For this next part, I'm going to make some assumptions that make sense to me, if someone has real data here, I'd love to see it, but they seem within the realm of reason.

Say these smaller coins are more profitable than a large coin 50% of the time (I think this is high), and are more profitable by 50% (also a bit high).  And we switch 5-10% of our pool to aim for them (500MHs-1GHs).  You're looking at a 1.25-2.5% boost to profit, without taking into consideration any of the context switching.

While I'm not certainly not against a 2% (or so) boost in profitability, the sheer cost of tracking all of these coins on all of the endpoints, and the cost of building something that accurately watches the hashrates and pushes the right amount on and off of those coins, doesn't seem like a great use of time (at least at this point).

Thoughts?

If you are living in Europe, take Wafflepool (stratum Amsterdam). But if you are living in US, test clever.. (no stratum in Europe).

maybe clever is doing better now (but what counts is a longer period), maybe they are calculated differently... doing your own comparison and math is always the best way.

why clever mining says 0.01247 per mh
but waffle only 0.00951912 per mh


?

How about just pointing all smaller miners (like >550k?) to the small coins permanently? Have a short list of all coins sub 10 diff that are only mined by a very small subset of wafflepool miners. If you set the variable to low miner hashrate, I would think this should at least be too slow to jump and repeat the issue which caused you to discontinue mining low diff coins.

Read a few posts up.

when will i get my payout?
13ZqW9JdVYugZegCvcGcdhbJQLwLFPR69Q

Which is exactly in line with the published BTC/MH daily rates. Whether this is good or bad, I just like the fact that this information is published on the web site. Then again, I guess if all pools did this choosing one wouldn't be so time consuming!

That really doesn't matter. Each share takes longer to accept, but is worth more. Submitting a 1024 share once every 20 minutes is similar to submitting a 256 share every 5 minutes. It all evens out in the end, you're not losing anything.

I'd probably be testing 64 and 128 for your rate though. My small rig is 1.0M and runs well at 64 or 128 with plenty of share accepted visual feedback stimulus!

That is some good info, and i can confirm my payout went out, still need to open my wallet and confirm, but great information on whats going.

Compared to MC, i havent noticed any issues what so ever, and i hope you are aware that a lot of MC miners have moved, and will move to Waffle over the coming days. As reflected by the increase in pool speed.

Keep up the great work!

I am trying to manually set the difficulty (have around 800Kh/s). But it takes ages for it to accept shares when I do that.

cgminer looks like this:
http://imgur.com/xCVqdwA
Happens when I set the difficulty between 256, 512, 1024

If I just leave the password to something else it looks like this:
http://imgur.com/xgGNbWw
Am I doing anything wrong? I had MUCH more shares accepted before..

Thanks for the efforts PW, appreciated!

Just got payment. Worked out to 0.0097137 BTC/MH. Will be trying some other pools for a few days.

thanks for the info...so yesterday drop in btc/mh was for this issue right??? and now its fixed?

Sorry for the delay in response guys.

Last night when the pool expanded about 10x in a couple hours, we had some continuous failures.  Simple explanation is that at about 8-10 GHs, things started breaking (a server would lock up every 5 minutes give or take).  So I spent about 18 hours straight, sitting here and manually restarting servers as they died.  All the while trying to figure out exactly what was happening.

Long story is that there were thread contention issues with the way we publish shares, and the way we publish blocks.  If on a distant endpoint (usw/eu), we were in the middle of publishing share data (takes about 100ms - every few seconds), and a block came in, packets could be ordered wrong, and the result was garbage data on the collecting server side.  Since there was no easy way to tell this programatically (other than watching share collection on the database, and restarting a server when its 10 second share-rate went to 0), it became a full time job to watch and restart servers.  Giving me a few minutes each time to try to piece together some code that might fix it.

At this time I believe the issue to be fixed, and should it happen again, checks are in place to rectify it quickly, although when it happens it could delay share processing and block processing by a few hundred ms (not terrible).  At the time I went to bed none of the servers had had the issue in 30min, and its now been a bit over 5 hours, and it looks to have only happened once (and corrected itself quickly).

Right now we're waiting for our withdrawal from cryptsy, so that payouts can go out in the next 30-60 minutes or so

It also looks like at this size, until we can get our difficulty-limited rate switcher in place, we'll need to stick to coins above 10ish difficulty.

I'm also going to run some numbers and see if it is even worth it to deal with the low difficulty coins at all.  My guess is that while sometimes they are more profitable (say by +50%), that will only last for a few blocks due to difficulty changes, and because they are low difficulty, they're not worth much per block.  So while you are getting +50% profit, you're only getting that +50% for at most a few seconds.  And losing 2 context-switch times in the process (1 from high difficulty coin to low, and one from low back to high), which easily adds up to more than a second or two of stales (0% efficiency).  I'll run some numbers and see.

bah i don't see it

why BTC per MH/s  falling  


why pool mining litecoin itself.......?

no its up

the web site is down?