something wrong with Uray US pool. Deadline becomes very high.
I think Uray change the pool now its becomes unstable.
is it better now? made some improvement
It was fine after a while when i reported the issue but now it's back again. See the pool site right now , most miner over 1000 years
ok, it should be fixed now
U can see the pool urself.
http://burst-pool.cryptoport.ioStill over 1000 years. In fact , its over 10,000 years.
Also, u might want to consider shutting down pool 3 since it has less than 100 miner. Ur profit will be better if there were only 2 pool.
Its back to normal now.
I wonder if your pool profit will increase if your only have 1 pool with good specs.
If u combine all pool into 1 , u can attract more miner than having 3 pool because most miner (like myself) like to join big pool due to stable payout. U should have about 500++ miners if u combine them , making it the biggest burst pool.
It is also easier for u to maintain 1 pool instead of 3
i provides 3 pools because each of them has different characteristics :
US Pool : for regular stable payout, but a bit slow in performance due to more miners
SG Pool : almost like solo mining, for miner that own very large capacity, high payout but more variance
EU Pool : for miners who want performance & reliability due to deadline limit
as for profitability, most of them are due to burst price factor, i still have faith in burst value, so lets wait and see
the error you mentioned was not performance issue, its just bug that when new round is triggered, old nonce submission was
not cleared in the queue, so the remaining nonces in the queue are checked against new block, hence the large deadline. but it seems to be fixed, i don't see any large deadline so far.
and the performance is quite good, i don't see single nonce submission failed on US and EU Pool, but i still see nonce submission failed on EU, but it could be miner using old miner client (java)
and please note that, if your miners say failed to submit nonce, its because the client does not receive reply from pool for specific timeout period, but the nonce is actually received by pool and added to the share, but when pool want to reply the deadline to client, the connection already closed