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

[azebro]

PW / cgminer experts,

I see strange constant behaviour on couple of my miners. Cgminer displays "connection interrupted" and just hangs there without even falling over to other pool (have 2 backup ones set). There seems to be no internet issue at that time.

I use EU server.

Its really annoying, as can happen from 0 to few times a day and my hash drops as miner does nothing at all.

Now the q is, what is the possible issue? Is it my end or the pool end?

If you're specifically talking about today (over the last 3 hours or so), I've been making tweaks across our clusters (eu is easiest to test with since it is lowest hashrate), so that might specifically be me.

Can you post your config to see why failover isn't working?

Thanks for the quick reply, here you go config for the one that does that the most:

cgminer.exe --scrypt  -o stratum+tcp://eu.wafflepool.com:3333 -u 1Y9My747MgN9jVovucztEKSgLengPrsm6 -p d=512 -o stratum+tcp://useast.wafflepool.com:3333 -u 1Y9My747MgN9jVovucztEKSgLengPrsm6 -p x -I 19 -g 1 -w 256 --thread-concurrency 24000  --gpu-engine 1100 --gpu-memclock 1500 --shaders 2048

thanks,
A.

[1714690953]

1714690953

[1714690953]

1714690953

[1714690953]

1714690953

[poolwaffle]

Thanks for the quick reply, here you go config for the one that does that the most:

cgminer.exe --scrypt  -o stratum+tcp://eu.wafflepool.com:3333 -u 1Y9My747MgN9jVovucztEKSgLengPrsm6 -p d=512 -o stratum+tcp://useast.wafflepool.com:3333 -u 1Y9My747MgN9jVovucztEKSgLengPrsm6 -p x -I 19 -g 1 -w 256 --thread-concurrency 24000  --gpu-engine 1100 --gpu-memclock 1500 --shaders 2048

I don't see a "--failover-only" setting in there, can you check while its running that failover is enabled (and that it has 2 pools in settings)?

[azebro]

Thanks for the quick reply, here you go config for the one that does that the most:

cgminer.exe --scrypt  -o stratum+tcp://eu.wafflepool.com:3333 -u 1Y9My747MgN9jVovucztEKSgLengPrsm6 -p d=512 -o stratum+tcp://useast.wafflepool.com:3333 -u 1Y9My747MgN9jVovucztEKSgLengPrsm6 -p x -I 19 -g 1 -w 256 --thread-concurrency 24000  --gpu-engine 1100 --gpu-memclock 1500 --shaders 2048

I don't see a "--failover-only" setting in there, can you check while its running that failover is enabled (and that it has 2 pools in settings)?

Yes, if I go the cgminer settings the pool strategy is set to "failover only". That miner has only 1 backup set, others have usually 2 backups, but the behaviour is the same ( most configs are pretty same as use mainly 270s) - connection interrupted, xxx shares lost and not failover

 

A.

[richmke]

Request:

I am trying to fine tune my rig, and hash rate that the pool sees is what I am trying to maximize. With the hash rate going all over the place, a daily average would be nice. What I am thinking is:

In the Recent Payouts list, can you also have a "Shares accepted" field. Either an ongoing number, or since last payout.

Then I can tweak my settings, run it for a day or two, and see a daily average.

Thanks.

[The Fat Miner]

I don't know what kind of sorcery you are doing, it's working. Back with Hashcow, MC-Asia server, I always had 5-7% reject rate, and CM, 10% easy, but with your uswest, I got 1-2%, mostly under 1%, and the WU is relatively high as well. I'm in China btw. So please don't change anything in the future, it's already perfect

And do you have any updates about when will the Asia server be up, really looking forward to it!

Glad its working well for you!

As for asia server, it was up like a week ago, and I never posted it anywhere (was testing).  Unfortunately at this point I've made enough modifications to the code that it is no longer a working server (was doing fixes on our other endpoints and asia got left out).  And haven't had time to go back and get it working again.  Maybe tomorrow is the day I do that

+1 for the Asia server, Would be much appreciated as I'm very far from any of the servers, And I imagine lots of others too.

[The Fat Miner]

Request:

I am trying to fine tune my rig, and hash rate that the pool sees is what I am trying to maximize. With the hash rate going all over the place, a daily average would be nice. What I am thinking is:

In the Recent Payouts list, can you also have a "Shares accepted" field. Either an ongoing number, or since last payout.

Then I can tweak my settings, run it for a day or two, and see a daily average.

Thanks.

I have been trying to achieve similar things, And I slowly realised you cant find the best settings, Because the coins are constantly changing, If you find out otherwise let me know and I would love to see what you have done.

[Axco]

If you are testing your settings may be try testing them on a dedicated single coin mining place to avoid the coin switching ?

[tblack]

Thanks for the quick reply, here you go config for the one that does that the most:

cgminer.exe --scrypt  -o stratum+tcp://eu.wafflepool.com:3333 -u 1Y9My747MgN9jVovucztEKSgLengPrsm6 -p d=512 -o stratum+tcp://useast.wafflepool.com:3333 -u 1Y9My747MgN9jVovucztEKSgLengPrsm6 -p x -I 19 -g 1 -w 256 --thread-concurrency 24000  --gpu-engine 1100 --gpu-memclock 1500 --shaders 2048

I don't see a "--failover-only" setting in there, can you check while its running that failover is enabled (and that it has 2 pools in settings)?

Yes, if I go the cgminer settings the pool strategy is set to "failover only". That miner has only 1 backup set, others have usually 2 backups, but the behaviour is the same ( most configs are pretty same as use mainly 270s) - connection interrupted, xxx shares lost and not failover

 

A.

Why don't you use cgwatcher? It is working fine for me. It have a lot of settings in it to maintain constant mining.

[mr_fakename]

+1 for this server in the asia pacific region, hopefully the data centre you've chosen in asia is a lower ping for me here in Australia, uswest and to a lesser extent useast aren't so bad but eu is definitely not Australia friendly at 350ms+ (although some pools and internet sites dream of being as low as 350 haha).

[poolwaffle]

+1 for this server in the asia pacific region, hopefully the data centre you've chosen in asia is a lower ping for me here in Australia, uswest and to a lesser extent useast aren't so bad but eu is definitely not Australia friendly at 350ms+ (although some pools and internet sites dream of being as low as 350 haha).

The server is actually physically up, just not active for mining.  You can test with a ping to see if its better (please anyone that tests that would normally use an asia server post results):

Saying it again, because some people don't read things unless its in bold and allcaps.
THIS IS NOT UP FOR MINING, ONLY TESTING FOR PING PURPOSES
ping sea.wafflepool.com

[GalacticMiningCorp]

Saying it again, because some people don't read things unless its in bold and allcaps.
THIS IS NOT UP FOR MINING, ONLY TESTING FOR PING PURPOSES
ping sea.wafflepool.com

+1 but it's going to have to repeated 5 more times over 3 pages

[The Fat Miner]

Saying it again, because some people don't read things unless its in bold and allcaps.
THIS IS NOT UP FOR MINING, ONLY TESTING FOR PING PURPOSES
ping sea.wafflepool.com

+1 but it's going to have to repeated 5 more times over 3 pages

It's giving me 63ms average which is miles better than any of the others, Over 330ms most of the time

[Sinyk7]

So read it however you want. Your btc/MH is fairly accurate there based on accepted MH, not your actual hash rate.

So did you earn more here or more on clever ?

I think I made more here? Last time I was doing a test run i had to shut my rig off for a couple hours, so it wasn't a fair comparison. I'm giving it another go now for the next 24h.

I know one day isn't a fair comparison, but I'm not comparing profits to profits, but rather what the pool says you should get per mh vs what you actually get.

You really have to take btc/MH values posted on sites with a grain of salt. It's easy to get caught up in the math when you mine at 3.6 MH and you see > 0.01 btc/MH per day, so you expect to see > 0.036 btc/day which is only true if you had a 0% reject rate. I might as well have unplugged one of my gpus with how much hashrate I was throwing away at clevermining.

Wafflepool is usually around 0.009 to 0.01. if my reject rate is as low as it usually is here, I should be slightly more profitable. Time will tell!

edit: as shares and value of coins changes all the time, my 24h profit at clever now reports as 0.03240274 BTC which works out to 0.01045 btc/mh (using 3.1 MH) or 0.009000 btc/MH (using 3.6 MH)

Figured I would update this:

I ran a 24h test on wafflepool to see how it compared to clevermining.

My earnings for the 24h stretch, taking into account unconverted btc value, gave me about 0.033366 btc which works out to be 0.009268 btc/mh (based on my actual 3.6 MH/s). This is also with only about a 1% reject rate.

So at least for my 24h to 24h comparison, which really isn't long enough by any means, wafflepool came out ahead slightly. Without being able to tell what my actual average accepted hashrate was during that 24h period, I can't give a true btc/mh reading but anyway, it seems fairly close to what is reported on the website's stats page.

In all honesty, they seem fairly similar in earnings, but wafflepool does seem a bit more transparent, albeit not as pretty.

Even mining VTC, at current prices, is almost the same as mining at wafflepool. When the price of VTC was higher, it was significantly more profitable to mine, but not so much anymore. Everything has evened out.

[Dawg75]

Request:

I am trying to fine tune my rig, and hash rate that the pool sees is what I am trying to maximize. With the hash rate going all over the place, a daily average would be nice. What I am thinking is:

In the Recent Payouts list, can you also have a "Shares accepted" field. Either an ongoing number, or since last payout.

Then I can tweak my settings, run it for a day or two, and see a daily average.

Thanks.

Have you tried using WAFFLEStats?  Its linked to on the miner page and includes an average hashrate. 

[Axco]

+1 I was just going to say the same, but I don't think it gives an average accepted hash rate as it does on cleverminings user dashboard?

[jordbaaer]

Quick update (noted at the top of the site as well):

If anyone is still mining on the base domain (wafflepool.com:3333) instead of the geo endpoints (uswest.wafflepool.com, useast.wafflepool.com, or eu.wafflepool.com), please change your miners to one of the new endpoints.  We will be disabling proxying from the base domain in a few days here (probably saturday) due to reconfiguring of some servers.

If you do not update your configs, your miners will be disconnected and will either connect to your backup pool (if you have one set), or just stop mining completely if you do not have a backup pool configured.

Im using GUIminer and just writing wafflepool.com in the host-address. When trying to write "eu.wafflepool.com" or "useast.wafflepool.com" nothing happens. Am I doing something wrong?

[poolwaffle]

Im using GUIminer and just writing wafflepool.com in the host-address. When trying to write "eu.wafflepool.com" or "useast.wafflepool.com" nothing happens. Am I doing something wrong?

Something is definitely wrong there.  All of those are valid locations (wafflepool.com soon to not be).  Can you ping them to make sure your DNS is resolving properly?

[WaffleMaster]

Why are the rounds 150m shares now? That's an increase of 150% from the normal 100 million.

[dogechode]

Why are the rounds 150m shares now? That's an increase of 150% from the normal 100 million.

150mill represents a 50% increase (not 150%) from 100mill unless I'm missing something here.

[poolwaffle]

Why are the rounds 150m shares now? That's an increase of 150% from the normal 100 million.

150mill represents a 50% increase (not 150%) from 100mill unless I'm missing something here.

Just targeting a round every 10 minutes.  I've been adjusting every so often (today was the bump from 100 --> 150, as the round time had gotten close to 5min).  Really no hard reason for it other than as round time decreases, the variance between rounds increases (we can only process shares so quickly).  And there is a minor increase in load on the server with shorter rounds (caches need cleared)