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

Hi Guys!

So wafflestats is/are dead?

Will it return?

LPC

Mooncoin is not a high rate profit coin at the moment.  Hold them until the block reward halves and watch markets

EDIT: which I am mining exclusivly

Thanks for the update I may return here although Mooncoin is doing splendidly I have already reached my ROI

New database is in place.  Everything went smoothly, although it took a bit longer than expected.  Mining was uninterrupted, and everything should be running on the new box

WOW,

Doge difficulty is over 2000....

The sawtooth display on the left is because wafflepoolmonitor.com was not able to download the data through the wafflepool API and not any problem at your end.

This issue has been resolved and such peaks should no longer appear in graphs from now on. 

Thanks for the update.

I'm still seeing the problem that I reported earlier where there are spikes between zero and maximum hash rate every 20 minutes. You indicated that this happens when wafflepoolmonitor is not able to get the data through the api from wafflepool for a address.

This seems to happen every day, for hours at a stretch. And in fact it's happening for me now. It started a little less than 5 hours ago.

When I go directly to the wafflepool.com tmp_api URL for my address, I always get back reasonable JSON.

I really like wafflepoolmonitor, but it's hard to get reasonable info out of it when it's in this broken mode.

I'm seeing some very odd traces from Waffle Pool Monitor:
Any one else seeing similar or is it a problem at my end?  I understand the two big up spikes - PW explained this on the previous page but the odd sawtooth display on the left is odd
Thanks
Miles

Any one else seeing similar or is it a problem at my end?  I understand the two big up spikes - PW explained this on the previous page but the odd sawtooth display on the left is odd

I have to say, you are by far one of the best pool operators when it comes to communication.  In a crypto-world where everyone loves to yell 'scam!' at the first sign of trouble, it is good to get a clear and concise heads up when things will be slightly out of the ordinary for a small amount of time. 

Keep up the good work!

OK, Here's a heads up for everybody.

Our master database has been getting closer and closer to its limit over the past month, and instead of waiting for it to die fully, I've got a new one spooled up and ready to go.  Its about 4x as big (in terms of performance), so we should have a large amount of head-room for the future.  Ideally we'll be moving over to the new server tomorrow afternoon if everything in our tests goes correctly.

This shouldn't affect any miners, but will possibly affect anyone pulling stats from our API during the cut-over time.  Shares from endpoints are logged to a share-collector before being processed into the DB, and that share collector will be unaffected.  Most likely you'll see stats stop updating (if you're looking at a 3rd party stats site), or you'll see our webpage go down with a "Maintenance" banner.

Once we swap over to the new database completely, all of the pending shares will be processed, so you might see a drop in hashrate, and then a huge spike in hashrate, this is expected just because of the delay in processing shares.

We don't expect the cut-over to take more than 15-30 minutes, but it could possibly take up to an hour.

If anything were to happen that would cause a loss of shares from stratum endpoints (not planned), I will shut off the stratum endpoints entirely, and your miner will failover to a backup pool until we're back up and running.  You have a backup pool configured, correct?