this pool thief!!!!! 
I use 24 hours; he did not even make half the money he needed to give.
i tried with 1070ti.
https://resmim.net/f/e3YDhc.jpg i used ltc change
https://resmim.net/f/7orq08.jpg
sorry for bad English..
I use 24 hours; he did not even make half the money he needed to give.
i tried with 1070ti.
https://resmim.net/f/e3YDhc.jpg i used ltc change
https://resmim.net/f/7orq08.jpg
sorry for bad English..
You used one of the most volatile coins for test, but you might be right, because on zergpool you will always get less actual BTC real payments that inflated values from estimates that you expect to get. Below is the solution for your problem.
The only solution is to have every day test miners (with a single gpu each - you get the same results if you use 12 gpus for each) on all pools with different wallets for each pool. The wallet for the pool with the best BTC payment performance will be used for the rest of your rigs. After a few weeks you can rotate wallets and you won't loose even the small values you have on these wallets.
Any other statistic that is either current, 24h estimate or 24h actual has no relevance when you compare with this method. Pool administrators must respond in minutes to forks or issues and the pools that are failing to do this have bad BTC payments when you compare with statistics that made that pool be in the top of estimates when mining.
Pool fee has zero relevance also, because besides visible fee, there is another parameter that is called EXCHANGE_FEE and some pools have high values for it (it is 6% and 10% for others, and some might have it at 0%, you can not know, you must see real payments).
I hope everyone use this method because it's the best. To use it, you just have to select just one GPU, because if you use 1 gpu or 12 gpus for this test, the difference between pools is exactly the same.
With this method you do not waste your money and with 6 gpus you can test 3 pools with both current and 24h estimates.
This method is also bulletproof to any trick pools might use like: inflating estimates, editing the code (you only have to edit one line of code and pools can steal 10% from all your income) , changing database values, and many others.
I also suggest to Patrike to implement a variation of this solution besides others he has in mind, because pools are not fair, and real payments are the only fair part you can check and evaluate pools.
Let me know if you find better solutions
