please at least close registration until it is fixed for 24 hours, thanks for your effort.
stales are jumping up and down for me - it is fine for 10 minutes, then terrible for 30 - I am way short of the 300 coins projected for 24 hours,
maybe try to cap the growth until there is more confirmation issues are fixed?
I think it's fixed now, but I'll close it until it's solid for 12 hours or so.
Just curious, what sort of a hardware spec do you need to support a 1,200MH/s pool rate?
It takes about 2 decent cores and 3GB of ram. But the real challenge is tuning mysql for low latency queries and dealing with misconfigured miners, botnets, and other trash that gets stacked against the server. One guy had like 800 open connections to my server
have to fight that stuff.
I run on a dual xeon L5420 right now with 8GB of ram.
load average: 0.86, 0.68, 0.64
Mem: 8197352k total, 7893208k used, 304144k free, 161604k buffers
Swap: 16009208k total, 16908k used, 15992300k free, 5837600k cached
Bandwidth is like this, the spikes are the offsite backups going out.
Paul, it is better than before but still problems for me -
I have sat watching various machines from the terminal (*eyes hurt*) - I see what is happening -
cgminer is fine for 150-200 or so accepted shares, no hardware errors occur, then there will be a cycle of
".......rejected
.........rejected
..........rejected"
between 6-15 times in a row, then
"failed to connect to stratum..."
it sits for a while then
"new block
..........accepted
..........accepted
..........accepted"
it starts over and each worker gets 100-150 accepted shares in row with zero hardware errors.
this behavior does not occur on give-me-ltc, coinotron, or other sCrypt pools with the exact same mining configuration.
is there some special configuration this site requires that I overlooked? It is causing my overall averages to be horrible, where at other pools my hashrate is essentially constant when using stratum.
Thanks if anyone can offer solution. Also this did not happen on this site when FTC launched.
---edit----
to be clear this exact same thing is happening across different rigs, with varying GPU hardware( mix of 6 and 7 gen), all AMD though.