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

The Fat Miner: I doubt my current issue is the same as yours.  I could restart my rigs and would have 100% shares counted again, but restarting these rigs is a royal pain in the ass because they are at a remote location and sometimes they don't restart properly.  So, I'd rather lose hashing power for a bit and have poolwaffle figure out why this is happening.

Looks like it might be affecting our big miner as well?  Their hashrate just fell down to about half...

I just saw the same problem, running on uswest server. Miners reported working fine, web stats showed zero work.

I restarted the miners and things look to be correct again.

Test for longer then 5 hours before complaining?  Yeesh...

That said, something is weird PoolWaffle - half of my shares aren't being counted right now, started just after 18:01 server time.  Shares are still be submitted by all my rigs, but half aren't being counted by the site stats (it appears 2 rigs in particular probably aren't getting their shares counted).  I have seen this before once a few days ago, and had to restart the machines.  Everything is pointed to uswest, but my rigs are divided between two locations - the second location seem to be what isn't being counted right now.  I will leave them without rebooting for a bit, so you can maybe take a look.

Wafflepool hash: 1625dbc1
worker names I suspect are not having their shares counted: phzi1, phzi2

That said, something is weird PoolWaffle - half of my shares aren't being counted right now, started just after 18:01 server time.  Shares are still be submitted by all my rigs, but half aren't being counted by the site stats (it appears 2 rigs in particular probably aren't getting their shares counted).  I have seen this before once a few days ago, and had to restart the machines.  Everything is pointed to uswest, but my rigs are divided between two locations - the second location seem to be what isn't being counted right now.  I will leave them without rebooting for a bit, so you can maybe take a look.

Wafflepool hash: 1625dbc1
worker names I suspect are not having their shares counted: phzi1, phzi2

5 hours of 2 Mh/s has earned 0.00225 , That's worse than what Middlecoin has been shafting me with,  And my rejects are blinding 0.58%, Efficiency 440% in CGWatcher , So something isn't right at all.

please enable fast coins , small coins

hi guys!

ive mined on MC for the past few months, but the recent shenanigans have made me switch, so im excited to see how this pool performs.

is there any official or 3rd party site with graphs similar to those available from MC? i would love to be able to track my hashrate and stats over time in graphical format

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 !

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)?

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.

Thank you for your feedback!

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 ([email protected]) 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.

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.