|
must... find.... block....
|
|
|
|
|
Just added capability to offload heavy stats to replicated server (less stress on your pool sql server).
|
|
|
|
|
Offloaded some heavy statistics to the replication server, should be less stress on pushpool now.
|
|
|
|
|
just put in a new field index, caused a brief (1min) unexpected pool outage.
Also, current stale shares were added to the stats bar.
|
|
|
|
|
More updates to v3 pushed to repo.
|
|
|
|
Hello, I am about to open registrations again  They should be open within 15 minutes. I've completed a lot of performance improvements (I hope) over the past week or so. Lets see what we can handle! There is still no mandatory fee, but this is subject to change in the future. I would of course give ample notice if this happened. Meanwhile, I appreciate everyone's donations!  I still haven't done all the math, but the pool is about breaking even at the current donation rate, hashrate, and server costs. However, I think I am still in red if you consider the 14 BTC starting bounties, etc. Just for those curious. Congrats, hope you scale nicely! |
|
|
|
Firefox  hmmm, I'll look into it. The menu is just css sprites. Update: Ah huge browser window, looking into it. Also, just rebooted. I'm bound and determined to iron out those stales some people keep seeing. |
|
|
|
About the new UI--
The top bar is dispositioned
What browser is that? I see no issues in chrome or firefox. Also, just updated pushpool to 5.1! Update: Patched 5.1 to have better long-polling support, should help with stales. |
|
|
|
About the new UI--
The top bar is dispositioned
What browser is that? I see no issues in chrome or firefox. Also, just updated pushpool to 5.1! |
|
|
|
|
Added a forum for discussion and support since I'm often afk in irc. Feel free to give your fellow admins help and share your solutions.
|
|
|
|
|
Couple of UI changes and...... I setup our own forum (It's ugly and basic, but it's ours).
|
|
|
|
Adding a replication server, might cause a hiccup... should be quick.
UPDATE: Done.... we not only have backups, we now have a live backup!
Cool!  So...this is a back up pool server? In the event of DDOS/Botnet/some other crash, with seamless switching? Not seamless yet. The replication is only 1-way to the server. |
|
|
|
|
Adding a replication server, might cause a hiccup... should be quick.
UPDATE: Done.... we not only have backups, we now have a live backup!
|
|
|
|
|
The lost password feature is now working
if your account has been banned for too many bad login attempts, this will un-ban it.
|
|
|
|
I have very high OC's on my cards! So when I "lower my clocks", I'm still much higher than stock!  yes, I think I was pushing past the oc limit for my voltage (running linux, so no overvolting) |
|
|
|
D@mn! I come home from work, and all my miners are stopped!  So I just got'em back up and running! I hate when that happens. I had to lower my clocks on my main machine, the cards kept dropping (not overheating). |
|
|
|
Button "Lost Password" is there just for anturage? I haven't found any code serves this event...
It's just a relic from mining pool v1.... Looks like it was a stub. I'll get to it in the next version. Which reminds me.... v3 features not yet in repo: Memcached support No more shares_history (what a nightmare that was) Improved block handling. Dynamic stats/setting caching (more responsive/less overhead) Process locking Drastically improved cronjobs. Live round stats. Just to name a few improvements.... Looking forward to seeing how you have tackled this.... im in the midst of dealing with these same issues... especially the whole shares_history nightmare and the associated monster queries. Good news then.... I just pushed the initial v3 to the expiremental repo. This is no upgrade script, nor a simple upgrade path... yet. You'll need to merge these as appropriate. As for moving shares history back into shares (AFTER adding new shares fields), I used this sql: INSERT INTO shares (username, our_result, time, blockNumber, score) SELECT username, our_result, time, blockNumber, score FROM shares_history WHERE shares_history.counted = '0' Also, I recommend using a separate instance of memcache than pushpool. Don't want your pool cache eaten by web data. |
|
|
|
all my workers on the account detail are red though they show a hash rate weird...
Yep, missed that last night. I'll have it working shortly. UPDATE: Added some load balancing to up site/pool performance. |
|
|
|
|
About to try out nginx web server. The pool will be up but the website may be unreachable for a few.
UPDATE: Unrelated pool trouble.... looks like a network issue at the datacenter.
UPDATE #2: back up. couldn't reach any of my sites there for a minute.
UPDATE #3: Round shares & estimates showing 0, working on making that stat less resource intensive.
UPDATE #4: Everything's happy again. Network issues may have only been on my end, as I don't see a real drop in anyone else's hashrates.
|
|
|
|
Hey! It's cool that the top 30 hashrates doesn't show inactive people anymore, but it looks awkward for the Onion winners to be below the Top 30 most shares.
Working on it I've pretty much rewritten about 50% of the back-end in the past few days. While the site looks mostly the same, the operation behind the scenes is vastly improved. |
|
|
|
|
Show Posts
