Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 167. (Read 903163 times)

I spoke with eleuthria and the local math wizard organofcorti and they both confirmed there is no easy way to precisely confirm the pool luck, which is a deal braker for me.
I guess it is just a psychological barrier for me to join a pool, where I cannot verify one of the main factors that determine how much I earn.

I don't think the main idea behind the 1.5% perk is to get paid for the orphaned block. If it was nobody would have paid the fee because for the last 1600 blocks there were only 3 orphaned. That's only 0.1875%
I know I don't pay it, because I am OK with waiting 120 confirmations for a new block.

Anyone know if it is possible to get or calculate the PPLNS Pool Luck via the API?

Only Deepbit (3% prop) and BitMinter (if you pay at least a 2.5% fee).

If you want the same features, BitMinter is the same fee (Orphans+Idle Warnings require a 2% "donation" on top of the 1% fee).  Slush is effectively higher fee (orphaned blocks + namecoins are worth much more than the 1% fee difference).  Leaving you with Eligius and GHash.io as your only alternatives if you don't want to deal with extremely small pools.


EDIT:  Forgot Deepbit doesn't pay transaction fees.

Does anyone know of any other btc mining pool that does pay for orphan blocks and transfer fees back to the miners?

Just asking.


Icon

The EU filtering server was suffering during the outages.  This was fixed shortly after the website was restored.  As of this post, all servers (including the DDoS/Botnet filters) are running optimally.

Alright, everything has been running smooth for about 30 minutes now.  I think I've killed off all the offending queries, and there's some extra work being done in the background to hopefully prevent it from happening again.

== Below This Line May Be Useless If You're Not Familiar with Databases ==

The problem stemmed from a JOIN based query used in looking up PPLNS Stats.  This query was not a problem until just recently, and was caused by the growth of the pool making the result set from this query become too large for a memory table.  As a result, the query was forcing the result set to be written to a temporary disk based table.  This query executes a LOT, and it's unique per user because it's the query which displays a user's stats for recent shifts on both the Dashboard and PPLNS Stats page.  This ended up causing table deadlocks if too many instances were accessing the table at once.

It took a while to diagnose because I was operating under the assumption the writes to that table were causing it (block rewards, shifts being closed, etc).  However, in this case it was the reads causing the root problem.  The writes were just the catalyst to cause the eventual table deadlock.

Once I confirmed the specific queries that were causing it, I was able to get in and rewrite those queries to use smaller result sets and multiple queries, rather than a single query to get all of the data at once.

== End Technical Explanation ==


So far it's looking great, but I'm leaving the monitors up for the rest of the day to check for any abnormally long queries, so hopefully if it is not fully fixed, I will be able to pause the website again before it creates an actual deadlock.  I'm also adding a new external alarm to set off my phone if a similar error happens in the future, since this particular failure did not trigger any of the already existing alarms.

I really haven't had any trouble mining, just could not see web page. Been submitting shares all day. Currently connected and all looks well for me.

I'm with you Brother!  I'm almost out of the negative now. 

My KNCMiner is on a circuit that's loaded nearly 100% of it's capacity but today my breaker tripped as the website was down, other miners fans spun down and KNCMiner overloaded the circuit. Drove to work to fix the problem, couldn't connect to the pool after that. Now mining at backup pool.

Feels surreal needing to mine out a deficit 

Looks like I picked the right weekend to have to RMA my Cube.

GL getting everything stabilized, eleuthria, and thanks for the excellent communication.

The API is still running during the website maintenance/update, just an FYI.

WAAAAA I can't obsessively click on the dashboard to watch my stats!!!
 

Mining is confirmed to still be operational.  Future fixes should not require any additional restarts of the mining server.  Unless something goes wrong, the only thing that will have intermittent service is the website itself.  Shutting off the website provides a SIGNIFICANT boost to how fast operations can be done on the database, mostly because the website is essentially under 24/7 attack these days so there is a lot of database load all the time.


UPDATE:  Problem has definitely been found, now working on fixing it.  Pool servers are still online and functional, just keeping the website off a little bit longer.

Agreed!

Maybe a little patience is in order?  El is as good as they good for pool ops.

M

The joy of errors that can't be reproduced in a test environment.  Going to be spending the rest of the day staring at scripts and turning them on one by one.  Website will be back in a few minutes once I confirm we didn't have another repeat of the multiple block payout.

I seem to still be mining on BTC Guild but the web site appears to still be down.

There are still issues, showing cloudflare for the website here ... I appreciate your efforts, but this is really unacceptable given the amount of fees that are collected.