Topic: Solo mining WDC 1600Kh/s - Lot's of rejected blocks (Read 2996 times)
and if all else fails with solo mining, feel free to join any of the awesome pools that are up
Pool operator experience tells me
1) Incoming connections (port forward) are good
2) The default outgoing connection limit is bad for fast blockchains
3) There is no fool proof way to prevent orphans or stales, especially if the major pool operator doesn't take steps to make well connected nodes
So
Forward your ports
Recompile your xxxcoind with net.cpp modified to allow 100+ outbound connections and raise the incoming limit to 500 or something, you'll use about 500kbit/s of upload with 500 peers.
1) Incoming connections (port forward) are good
2) The default outgoing connection limit is bad for fast blockchains
3) There is no fool proof way to prevent orphans or stales, especially if the major pool operator doesn't take steps to make well connected nodes
So
Forward your ports
Recompile your xxxcoind with net.cpp modified to allow 100+ outbound connections and raise the incoming limit to 500 or something, you'll use about 500kbit/s of upload with 500 peers.
Cheers, i'll give it a try. Is it just port 11082 i need to forward?
Each coin uses a unique port, keep that in mind if you change coins.
yeah, If that's your wallets port.
K.
K.
Cheers, i'll give it a try. Is it just port 11082 i need to forward?
Thanks for the reply. Do you mean forward the ports on the router?
I haven't messed about with port forwarding since my counterstrike days, but i should be able to work it out.
I haven't messed about with port forwarding since my counterstrike days, but i should be able to work it out.
Yeah, the cleaner and faster your connection, the less likely you'll get rejects.
K.
Thanks for the reply. Do you mean forward the ports on the router?
I haven't messed about with port forwarding since my counterstrike days, but i should be able to work it out.
I haven't messed about with port forwarding since my counterstrike days, but i should be able to work it out.
Make sure your ports are forwarded, and firewall is not blocking anything - your internet connection can have that effect.
K.
K.
Hi,
So i'm solo mining WDC and i seem to get about double the amount of rejects than i do accepted.
I'm not sure how much this is affecting my actual income, as for example yesterday i got 12 blocks accepted (about 25 rejected) - and on average i should of gotten 15 blocks, so not far off, plus the difficulty went down during the day so 15 blocks was for the new lower difficulty.
Sometimes i'm not finding an accepted block in 6+ hours when i should be finding one about every 1.5 hours, could be luck though (lot's of rejects found though, as i say, too many).
I'm using the following for my 7970's and my 6850:
cgminer --scrypt -o localhost:11082 -u xxxx -p xxxx -d 1 -d 2 -s 1 --expiry 1 --queue 0 --thread-concurrency 20992 -I 13 -w 256 -g 2 --lookup-gap 2
cgminer --scrypt -o localhost:11082 -u xxxx -p xxxx -d 0 -s 1 --thread-concurrency 6144 -I 16 -w 256
Anyone any idea what's going on?
I've had people tell me it's due to the short block time and someone else finding a block slightly before i did - but this doesn't explain why if the amount of rejected blocks were actually accepted, i would be making way over predicted.
Cheers
So i'm solo mining WDC and i seem to get about double the amount of rejects than i do accepted.
I'm not sure how much this is affecting my actual income, as for example yesterday i got 12 blocks accepted (about 25 rejected) - and on average i should of gotten 15 blocks, so not far off, plus the difficulty went down during the day so 15 blocks was for the new lower difficulty.
Sometimes i'm not finding an accepted block in 6+ hours when i should be finding one about every 1.5 hours, could be luck though (lot's of rejects found though, as i say, too many).
I'm using the following for my 7970's and my 6850:
cgminer --scrypt -o localhost:11082 -u xxxx -p xxxx -d 1 -d 2 -s 1 --expiry 1 --queue 0 --thread-concurrency 20992 -I 13 -w 256 -g 2 --lookup-gap 2
cgminer --scrypt -o localhost:11082 -u xxxx -p xxxx -d 0 -s 1 --thread-concurrency 6144 -I 16 -w 256
Anyone any idea what's going on?
I've had people tell me it's due to the short block time and someone else finding a block slightly before i did - but this doesn't explain why if the amount of rejected blocks were actually accepted, i would be making way over predicted.
Cheers
Jump to: