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

[poolwaffle]

During that time, they were offline fully, however they were all offline at the same time (much easier).  Didn't expect it to take multiple minutes, only expected a few seconds of downtime.  Just ended up needing to fix something real quick as it didn't act as expected (and took a couple minutes)

[1714666227]

1714666227

[1714666227]

1714666227

[1714666227]

1714666227

[1714666227]

1714666227

[coyote]

During that time, they were offline fully, however they were all offline at the same time (much easier).  Didn't expect it to take multiple minutes, only expected a few seconds of downtime.  Just ended up needing to fix something real quick as it didn't act as expected (and took a couple minutes)

Hi - my rigs were reporting connected & showing shares being accepted without any appearing on the website. Are you sure they were completely down? If so I need to look at why cgminer carried on for over 10 minutes without failing.

[Monopoly]

Hello ,
I use HD 7870 for mining and my hasrate is 340 Kh/s in CGMIner with full stability . but the site pool shows my hashrate minimum 80 kH/s and maximum 140 kh/s . Has got the site problem ?
In the last three days i just earned 0.003000 BTC but when i calculate by the site's states i should earn 0.01  BTC

Check your cgminer HW errors, also take a look at your WU... Report here.

Hello ,
Here's my Cgminer after 5 minute mining :

[oktay50000]

hw=225 and incresing
is tooooo highh

[vm_mpn]

hw=225 and incresing
is tooooo highh

Yes, something is not right with your config... You should not see HW errors.

Have you consulted this? https://litecoin.info/Mining_hardware_comparison

[LPCobris]

Hi!
Thanks for your great support and communication PoolWaffle!

I have a question!

Yesterday i move my operation to your pool.

They are 3 machines:

Machine1: 1.7 Mh
Machine2: 2.2 Mh
Machine3: 2.3 Mh

Total: 6.2 Mh

Its normal that is reported a little low then that? like 4 MH or 5 Mh max?
Can you see that here!

- http://waffles.wilschrader.com/stats?address=1KjJGtmpEEkz6GYRC2CtgKFc4jaiqR1qjB

All the machines are working normally at full steam (clients showing that hash rates).

Thanks in advance and keep up this great work! Thats a big chance from MC where i come!

Best Regards,

LPC

[Monopoly]

hw=225 and incresing
is tooooo highh

hw=225 and incresing
is tooooo highh

Yes, something is not right with your config... You should not see HW errors.

Have you consulted this? https://litecoin.info/Mining_hardware_comparison

Thanks a lot . I didn't know HW is very important and anything other than "0" for it is a huge problem . Now i'm changing my config and everything is okay . Thanks again .

[Space3003]

Hi!
Thanks for your great support and communication PoolWaffle!
I have a question!
Yesterday i move my operation to your pool.
They are 3 machines:
Machine1: 1.7 Mh
Machine2: 2.2 Mh
Machine3: 2.3 Mh
Total: 6.2 Mh
Its normal that is reported a little low then that? like 4 MH or 5 Mh max?
Can you see that here!
- http://waffles.wilschrader.com/stats?address=1KjJGtmpEEkz6GYRC2CtgKFc4jaiqR1qjB
All the machines are working normally at full steam (clients showing that hash rates).
Thanks in advance and keep up this great work! Thats a big chance from MC where i come!

Best Regards,

LPC

5788kh looks oke now

[oktay50000]

what worker diff is okay for 1x 7950 ?now its on 256

[igroock]

 was curious about the diff as well. i run 280x cards. what should it be set to?

[pallas]

was curious about the diff as well. i run 280x cards. what should it be set to?

It depends on the total hashrate of the rig, not the single cards.
And it actually matters very little in the long run; I'd stay with 256 or 512 if more than 5 Mh/s.

[jaybee3014]

What if I have 4 different rigs, totalling 2.7Mhs, but one has 400MH, the other 700MH, etc, all pointing to the same BTC address? Should I just leave "x" in this case?

Overall you're better off setting a hardcoded difficulty.  Lowers the work on the server overall, and if/when you disconnect, you don't start back from the default difficulty and ramp up.  I'd personally use 64 for the 400MH, 128 for the 700MH, and 256 for anyhting around 1MH (512 above 1.5ish?).  Theres no right answer, they'll all work fine, just a bit differently (more/less variance, more/less network connectivity, etc)

Do you mean 400KH and 700KH?

Pool:  When talking about the KH and the MH, are you referring to the overall miner total or each individual card?  I am running a total of four cards on one rig totaling ~1.8MH.  After reading your post, I set my diff to 256.  In your opinion, is that a good setup for me? For the past week or so (since I have been on your pool) I kept it as X and let your servers decide for me.  Thanks, and keep up the good work....last two payouts have been good.

EDIT:  After running the 256 for about and hour or so...I have noticed two things.  1)I get quite a bit of work restarts.  2)I get quite a bit of detected new block.  This appears to lead me to my concern....cgminer is reporting what appears to be a lot less accepted work since the change.  I am at about .5% reject rate on 1.8MH/s.  Is this normal, or is there currently an issue on your side?  ...OK just looked again and now ive got like 10 straight accepts...it seems to come and go in spirts.  Is this normal?  Thx.

[oktay50000]

was curious about the diff as well. i run 280x cards. what should it be set to?

i have 6 rig
5 of them are 280 with diff set to 512 and working great
but adding another 7950 rig anad for now only 1 7950
and i dont know which is better 128 or 256

[glon]

Hmm I noticed that in spite of manually specifying d=64 for my 400KH miner, the cgwatcher window is now reporting a difficulty of 16 ... weird?

Edit: same problem on one of my 700KH miners where I manually set d=128 cgwatcher was showing first 128, then 16 and now 64?? Perhaps it's best to just leave this stuff on auto?

[oktay50000]

Hmm I noticed that in spite of manually specifying d=64 for my 400KH miner, the cgwatcher window is now reporting a difficulty of 16 ... weird?

Edit: same problem on one of my 700KH miners where I manually set d=128 cgwatcher was showing first 128, then 16 and now 64?? Perhaps it's best to just leave this stuff on auto?

no its ok for me i set 256 an dits working for day on 256

[Uniphase21]

I am mining one rig with an average hashrate of 1.785 mh/s. I am having a reject rate of 1.88%. Is this abnormal?

Also yesterday I logged in and have found 21 blocks and today it went to zero found, is this an error on the site or is my machine having a problem?

[phzi]

EDIT:  After running the 256 for about and hour or so...I have noticed two things.  1)I get quite a bit of work restarts.  2)I get quite a bit of detected new block.  This appears to lead me to my concern....cgminer is reporting what appears to be a lot less accepted work since the change.  I am at about .5% reject rate on 1.8MH/s.  Is this normal, or is there currently an issue on your side?  ...OK just looked again and now ive got like 10 straight accepts...it seems to come and go in spirts.  Is this normal?  Thx.

Work restarts and new blocks have _nothing_ to do with your worker diff.  That's just because we are mining a fast coin, or switching between coins quickly.  Periodic rejects are normal (it happens when 2 blocks are found within seconds of each other, or a new block is found and then we switch coins right away).  Under 1% reject rate is great.

I am mining one rig with an average hashrate of 1.785 mh/s. I am having a reject rate of 1.88%. Is this abnormal?

Also yesterday I logged in and have found 21 blocks and today it went to zero found, is this an error on the site or is my machine having a problem?

That is a fine reject rate.  You could probably tune your rig a bit for a slightly lower rejects (set expiry to say 5, and queue to 0, and maybe lower xintensity slightly or use 2 threads if possible), but for say a 1% gain in accepted shares, it's not likely to be worth your time.

[igroock]

was curious about the diff as well. i run 280x cards. what should it be set to?

It depends on the total hashrate of the rig, not the single cards.
And it actually matters very little in the long run; I'd stay with 256 or 512 if more than 5 Mh/s.

2.8 per rig x 5

[chilin_dude]

So a quick status update for you guys.

First off, pool is good and stable for the time being (hooray being able to handle an 8x pool expansion overnight!)

Second thing, I've temporarily disabled coins with difficulty under 10 (even 10 may be a bit low).  Essentially under this difficulty, we're fighting ourselves with orphans due to average block times, and network propagation rates (read: lower profitability). 

Our system does support mining multiple coins at once, but not at quite the fine-grained detail we would need to make these coins work, it was built to switch off like 25% of our hashrate to a coin, and leave the bulk on a larger coin, which was fine until now.  Now however, 25% of our hashrate is still way too much to put on a single coin.  So for the next couple days, while we get the switcher a bit more intelligent, we'll be mining some of the larger coins (10+ difficulty for now), which we'll lose out on a tiny bit of per-block profitability, but should win overall with the decrease in orphan blocks (read: higher profitability overall for now).

Past the switcher upgrades, we've almost finished setting up another stratum endpoint (singapore), and will let you know when that is up

And one last thing.  I've noticed some dips in worker counts, and it looks like certain groups of workers will be connected for a while, suddenly drop, and reconnect a second later.  I have some theories for what could cause this, but no hard data, as it is extremely difficulty to track down.  If anyone is seeing a reasonably consistent (and ideally time-based) disconnect/reconnect pattern on their miner(s).  Please email me (poolwaffle@gmail.com) with your miner's IP address, and which endpoint you're connected to, it would help me to track it down if I can watch a few specific miners that are experiencing the issue.

Any plans to implement say 10% of the hashrate being directed to X coin that has low difficulty but is super profitable compared to the bigger cions? Could have 10% on 3 diff coins and the other 70% on one of the bigger profitable coins (doge etc)?

[yslyung]

personally i like & love to eat waffles !

wafflepool you rock ! switched from MC (too slow & not much info) to CM (rejects are horrendous) & waffle is the best ! love the site response. really fast !

been around for sometime in bitcointalk but hardly post here but i couldn't resist ! joined waffle to grow. i'm sure this thread will go to the moon anytime soon.

directed 4.57 & 3.66 mhs rigs set to d=512 & d=256 (am i doing it right ?) & looking fwd to see some coins soon. very good replies from waffle especially support. 2 thumbs up !