Suggestion: Display a luck calculation for 24 hours, 7 days, 30 days. We're spending a lot of our mining time now trying to get big (profitable) dogecoin blocks, which is great, but since we haven't hit any our luck is probably negative. Showing the luck will help reassure miners when rewards are low due to randomness.
EDIT: Also, can we add MEOW. Seems to be the hot coin now and a good fit for this pool. (Assuming coinedup is supported as an exchange.)
We're not using CoinedUp yet, but I'm working on adding them (exchanges are our next major bottleneck).
As for luck, wouldn't be too tough, just a matter of recording mining time and switches (not currently being recorded), not sure how to do the actual calculation for some coins however. Basic luck is easy, luck with variable block rewards changes the mental association with the resulting numbers however. 100% luck on litecoin means something, 100% luck on doge, where every block was a low reward block (100k or so) means something completely different, even if the raw stat is correct.
Also wondering if we're switching too fast between coins? Regularly see the pool jump to a coin at #1, then falls to #3. The pool automatically switches to the new #1, and 30 seconds later the coin we were originally on jumps back to #1. I may be wrong (and probably am, but thought I'd ask), but would an additional test before jumping coins be appropriate? Maybe make sure that the coin we're on drops more than 500-1000 in profitability? And/or until the next block is found? Or maybe leave a % on the old coin until an additional test passed? I know you're working on testing a more aggressive solution, so my question may be completely irrelevant, but just thought I'd ask.
This is just an issue with display. Instead of changing the actual pool server to spit back numbers and amounts of hashrate going to various coins (tougher to test, requires a server restart, etc), the chart of coin mining hashrates was just a quick little hack that looks at the last 1 minute of shares submitted in the database. What that means is that once we switch, the stats look to lag behind a little bit, even though the hash power has completely switched. 10 seconds after a switch for example, the stats will show 50/60 seconds of the last minute's hashpower going to the coin we were previously mining, and 10/60 going to the one we're actually mining at 100% speed. We could look over a shorter period without a problem, but the rates become far more skewed by variance.
Add to the fact that the pool server buffers share inserts to lessen DB load (batch inserts), and it delays those stats by a bit more (5-10 seconds of shares buffered before the DB reflects the submitted shares), and those stats end up a bit delayed. But again, this is all just a visual thing, hashrate switches far quicker than those charts show.
Take a look at what hashcows is mining from time to time. it tends to be coins you don't have listed yet.
Noted, soon as we get the new exchanges up and running and tested (the tough part), we'll be adding more coins for sure!
Can you provide some info on the server(s)? Locations, etc?
Servers are currently in New York. Not sure what other information you'd like there (or how much more I'd like to make public)
We'll be adding more as time goes on for geo-loadbalancing, but we haven't seen a huge problem with latency up until now, and until it becomes a problem, not something high on the priority list
