WAFFLEStats v1.1 - Workers Are Sexy Edition
Another day, another update!

Individual Worker Stats
Stats are now being collected for individual workers. The biggest thing is that WAFFLES will only store a worker's hashrate if it has been active in the last 7 days. Also, these stats will only show for resolutions of 1 hour and above because worker aggregation is both computationally and bandwidth intensive. Tweaking may fix this.

Preferences!
Color mode, chart range and resolution, and visibility of different elements of the charts are now all saved across refreshes.

Confirmed/Unconverted Summary Flip
Unconverted is now "on top of" the confirmed balance on the Summary tab. This gives you a better idea of when you will actually get a payout.

Other Randomness
1) Redis caches email addresses now and will throttle anything sent to them. This prevents getting flooded with emails under certain circumstances (like those that have happened in the past). It also prevents people from spamming themselves or someone else with emails.
2) Summary chart now reflows to the height of the window MUCH better.
3) Properly displaying kilo/mega/giga kH/MH/GH abbreviations.
4) Emails now come from wil@wafflestats.com[2] instead of waffles@wilschrader.com[3] . Small change. Check spam filters.
5) Random bug fixes (Details tab null values, clickable range/resolution button, etc).

As always, please consider donating. Server costs are high! People keep telling me to make some WAFFLES features premium only, but I don't want to do that! I'd rather work on new features instead of implementing a premium membership framework!

Donate to: 1Pr87ypYdG8eMTNUXR4rT1q2P1VJ7yu1b5

Good idea. I'll definitely take a look at it and give it a shot. :-)

Both, perhaps? I'm only running a single mongodb instance and mongo REALLY shines (apparently) when you replicate it and shard it. So I'm not using it perfectly.

The largest dataset is storing each datapoint at 1 to 5 minute intervals for two weeks. There are currently 27,294,278 data points for 4500 addresses. Each datapoint is 240bytes in size.

It's not so much hosting (well, it is), as it is the mongo database I'm hosting. I started using mongo because, well, it's the "new hotness", and I started this project to play with new technologies. The problem is, I didn't realize at the time that 1) This would get so popular, and 2) Mongo needs to have all data in memory for it to be at all efficient.

The database is now hosting ~8gb of data and ~4gb of indexes. I'm sure I could make that more efficient, but, well, at this point it'd be a lot more work than I think it's worth. Because of that amount of data, I need to run it on an AWS server with a LOT of ram, and those are a fair bit more expensive than the other servers I'm running. Every time I've had an issue with the site being slow, it's been because of mongo running out of ram to use.

MongoDB... only once. :-P

WAFFLEStats V1.0 - Summarizin' and Detailin'
Just going to get right to it:

Summary Tab
This new first page shows a stacked filled area chart for balances. This allows for a much cleaner overview of what you're currently earning than the previous line charts. It also overlays payments (green line), hashrate (red line), and the "payout threshold" which is yellow dashes.
The balances are all a shade of blue to help tone down the number of colors and to prevent overwhelming you with information. They are stacked so your "unsent" balance is now shown automatically.

The good thing about this graph is that you can see everything at a glance, but you can also turn things on and off as you so desire. Clicking the individual items in the legend will show and hide them. As such, I removed the show buttons.

Details Tab
This allows you to see your hashrate and balance/earnings details, as well as your payments. You can select the period for which it should calculate earnings. Anything else you'd like to see here just let me know and I'll try my best to add it.

Charts Tab
This is simply the old page that I left for those that like it more than what I added today. I did add payments to the balances chart.

Options
A much requested feature: NIGHTTIME MODE. This simply allows you to change the page and chart theme to a darker color so it's easier on the eyes. Much eye strain before.

Squashed Bugs and Important Changes
There were several bugs, some of which you only would have noticed were you a hashing whale. The various hashrate values now adjust for kHash, mHash, and gHash. Balances work no matter if you're earning above or below 1000btc.

I had to delete the payments history because it was storing values as local server time instead of UTC time and thus showing incorrectly on the charts. As such, I had to disable payment notifications for everyone. This was to prevent spamming the hell out of people when I turned the site back on. I'll likely re-enable them later today, but if you want to do so sooner, feel free.

Comming Soon
My todo list:

- Add currency conversion values to BTC values using the various exchange API's
- Add individual worker stats
- Cache last email time to addresses in redis to prevent spamming when database becomes unresponsive.
- Add ability to calculate time until you reach a value. For example, on the details page, select the value "0.01", and it will tell you the estimated time until you reach that amount.

That's pretty much it. Sorry for the downtime over the last few days. Database reached new massive sizes and the server had to be upgraded, and Amazon AWS was being unresponsive so I wasn't able to fix things immediately. Everything should be good now.

As always, please, consider donating. AWS is costly: I'm 15 days in to the month and my cost is $63. Holy shit, I didn't realize it was that much. Please, please, consider donating. Every little bit helps. I'll need to pull it down if I can't cover server costs with donations.

Bitcoin Address: 1Pr87ypYdG8eMTNUXR4rT1q2P1VJ7yu1b5

Annnnd, we're back. Sorry about that guys. Also, huge update coming tonight or tomorrow. :-)

Just a heads up guys, but WAFFLESTATS will be down probably until morning. I needed to upgrade the AWS EC2 instance and my instances keep getting AN INTERNAL SYSTEM ERROR HAS OCCURED whenever I try and launch a new instance and/or request a spot instance. What was supposed to be a simple: Backup database, stop existing instance, start new instance, reattach database turned into an hour of SYSTEM ERROR SYSTEM ERROR SYSTEM ERROR.

Sorry.

One balance value is a float value (unconverted, no quotes, not a string), whereas the other two (sent, confirmed) are still string values. I would prefer them to be float values as the string values were being formatted ("1,xxx.xxxxxxxx") and it broke my API for the big dogs that have received that much. :-P

I'm not sure I get what you mean. Is it reporting only one payout, or are you getting two different payout notifications?

You got it, I think. It's actually closer to ~4000 people every 1-5 minutes. The connections from my servers are being ended immediately and not just timing out like stale DNS records. I'm also personally seeing intermittent data points pop up. I'm almost positive that it's due to the new DDOS protection that's in place. I sent poolwaffle the IP's of the two servers that will be connecting to the API in the hopes that he can white-list them.

WAFFLEStats v0.8 - "How to Fetch" Edition

Hey guys! Just popping in to let you guys know what I've been working on. My day job has been putting quite a bit of work on my plate the last week so I've not had a lot of down time to add new features. What I have managed to push out, though, is quite exciting.

Server-Side Hashrate and Balance Fetching
The servers will now continue grabbing your current data in the background even when you're not on the stats page.

This has a few limitations:
1) Background-fetching only happens at 5 minute intervals. However, while on the stats page your stats are still updated and saved at a 1-minute interval level. I may reduce this slightly over the next few days as the bugs are worked out.
2) You must visit the stats page at least once every 3 days for server-side fetching to continue. For now this is to gauge load, and, like above, as I monitor server load and if people request it I may increase this to 7 days.

I'm also still trying to be very cognizant of load on both the api that /u/poolwaffle [+2][2] set up as well as people who stop using wafflepool/waffles leaving and background stats being essentially a black hole on server load for the rest of us.

Unsent Balance Historical Plotting and Legends
These ones are not as exciting, but a few of you have requested it. There is now an option to show/hide the unsent balance line on the historical chart, as well as a legend for both charts. Someone actually /yelled/ at me for not having a legend. I felt bad.

So, there are the changes so far. I've spent the last few days working on the fetching, making it load balanced across both servers etc. Also just spent the last two hours fighting a bug that I'd never experienced before because wafflestats was down.

Features I plan on implementing in the coming days:

• Dark/Light Theme Switching
• BTC Statistics (BTC/kHash, BTC per hour, BTC per 24 hour, etc)
• Payouts to graphs
• Improvements to layout for mobile and switching between range/resolution/visibility

As always, server costs are insane, and the current downtrend in pool mining profitability isn't helping. 5 days into the month and server costs are at ~$21. If you love, <3, and use WAFFLES, please, consider donating mining time or bitcoin to: 1Pr87ypYdG8eMTNUXR4rT1q2P1VJ7yu1b5

It is displaying as UTC. So, days "start" around 7pm EST, 6pm CST, 5pm MST, and 4pm PST. Next Sunday it'll be an hour later.

Augh, no, we're fine. Donations are covering costs pretty good. I appreciate them a lot! It remains to be seen how much this next months server costs will be with the upgrades I did -- but I think I'll be fine. The servers are fine too... load balancing and dedicated servers are not even skipping a beat when it comes to the load now.

No, the issue last night is a dumber one. I increased the restrictions on my security groups/open ports last night. Everything SEEMED to be fine after the switch. The issue came around midnight when redis was disconnected for whatever reason and it attempted to reconnect to port 6379 when in fact I had only opened port 6397. It failed, crashing node, which caused the server to die and not recover.

Stupid issue, but we're back up and running now!

Thanks, good idea, and done!

Hey guys, sorry the server was down and acting up for a large part of the day. It finally "gave out" under so much load and, unfortunately for all of us, I am super busy at work this week for the first time in a long time.

So, I went ahead and jumped up my costs quite a bit by starting up several more AWS instances. I now have an instance hosting nginx and redis, which load balances to two separate node instances, and then I have a dedicated mongodb instance running as well. I'm really hoping this keeps things running smooth for awhile. :-)

Was upgrading the app. It's back up now, and has a whole bunch of new changes. :-)

Haha, shhhhhhh.

I think the confusion comes from reported hash rate. People see their miners settling in at 40, 200, and 700, and expect to see, 940kh/s all the time. But what's easy to forget is that with harder work, when submitted, you get more shares. So while it takes longer to submit work, submitted work should average out to the same number of shares. I can't see my average shares over the last 2 weeks vs the last 8 hours. I'll just have to trust the math.

I think the biggest thing is this: Because shares per round is fluctuating so much, reported hash rate is also fluctuating. Shares over time should average out to being the same, thus reported hash rate should average out to being the same.

I should have just done more research before speaking. Sorry about that. :-)

Since you fixed diff to 512, my reported hashrate and shares have not stopped fluctuating. I have a smaller CPU machine mining at 40kh/s, a 660ti mining at 200kh/s, and a 280x at 700kh/s. My lowest reported hashrate over the last 8 hours (of no changes on my end) was 185kh/s, and the highest was 1500kh/s. My average is DEFINITELY less (about ~830 instead of ~920) over the last eight hours than it was the previous eight before that.

As a result my shares have been all over the place, sometimes as low as 5500 / ~100000000 per round, sometimes as high as 12000 / ~100000000 per round.

Is this averaging out to what I was getting before? Because from what I'm seeing it isn't. Would it not be only slightly more difficult on the network to allow for hard-coded client-side diffs as low as 256 and as high as 1024? That should cover most people.

ETA: Just look at my hashrate over the last 8 or so hours. There is obviously a huge difference in saw-toothing going on.

It's a great suggestion, but I deliberately designed the stats to function like this. I did this for several reasons:

1) I didn't want people to visit my stats once and then forget about it, meanwhile the stats continue to be downloaded. This was a waste not only for me storage wise, but for wafflepool and myself's network usage.

2) Related to above, but I didn't want to hit the API unless people were actually using it.

3) It was quicker to code it this way.

4) I figured that since people had their PC's on mining all the time anyways, if they wanted historical stats they could just keep the page open somewhere.

There's a way to get around this, of course, and that's by writing a bash script or something which will hit the URL: 'http://waffles.wilschrader.com/current/BTC_ADDR' every 60 seconds and then trash the results. I leave the finer details of that up to the user.

Now, I'd love it if poolwaffle would give me (all of us) access to historical data he's no doubt already storing, but since he has more important matters to attend to, I'll make do with what I have now. :-)

Sorry about that, guys! Server issues that are fixed as of a few hours ago. More details here.

For those of you that use this service that aren't over on reddit, I'd like to say thanks to those of you that have donated. I welcome suggestions and feedback, and, also, donations in the form of BTC or donated mining time are ALWAYS appreciated.

Wil