OOOOPS just checked that's a time zone issue.
|
|
|
HMMM thats strange I only show: 3 Blocks on 24th Ca local time 3 Blocks on 24th California local time. Thats great.
|
|
|
jedimstr I could not agree with you more. IYFTech needs to learn some decorum, or just plain how to be nice. He will flame any one on any form, if he does not think a post is right. With a attitude like that it is all a big negative and will run Great people from developing and or contributing there time and efforts, and that,s a shame. One can have a debate and still be human or even nice and still get there point across. It is just not right!!!!! Merry Christmas everyone. Enjoy the holidays with your loved ones. Remember Christmas is all about the celebrating the Birth of Jesus. Ok let the Flaming Begin.
|
|
|
Ok thanks, just to make sure this was normal...
|
|
|
When i first setup my node, the default address was receiving payouts when blocks were found, and now that has stopped. No miners were ever using the default address at all. What exactly would the node get payouts for if anything. This is a 0 fee node and i never have changed that since i started it.
If some one knows or have seen this please charm in.
Thanks.
|
|
|
I really like it to. Just wish the blocks were more consistent then every other day or 2, but every time i do the math it usually does close or better then Eligius.
|
|
|
I just cjecked the link you posted. I am doing great. Est is almost 3.6Th and i am averaging about 3TH according to my local pool hash rate.
Do you mine in P2pool only or are you balanced between morn then one pool.
|
|
|
In right about 24 hours my 7 S3+ have found 8 shares 1 orphaned. I did not think that was to bad.
|
|
|
In the last post are you saying that each miner should be a S3+ or higher per miner or a total of each user hash rates of all miners assigned the one payout address. I have 7 s3+ mining on my node and there all using the same Pay out address. this seems to work ok, or would it be better to assign each miner there own payout address.
I also have 5 S2 that are pointing to a other pool. that seem to average 8-9 blocks a day so they make about double what my 7 S3+ do on p2pool node.
|
|
|
windows seems to do fine, but my getwork latency stats are terrible 3.5 sec average and it should be less then .1
|
|
|
I am in the process of setting ip a Debian 7 now.
|
|
|
It is connected to a 1Gig E port on the office switch connected to a sonicwall firewall then a 100 Meg fiber connection, so i am kind of lost thats for sure. I am going to have to fine the ip and determine the latency to them. The latency to bitchain.info is only 7ms but i do know that has no baring on this issue,
|
|
|
Bitcoind is on 9.3 the node is running on Windows 7 64bit with 2 ea xeon quad core processors and 16 gigs ram. I got a screaming deal on these dual processor xeon quad core boxes. I installed a SSD drive to get this to run as fast as possible.
|
|
|
I have my node running much better, Efficiency is now 98% but my get-work latency still really sucks, but i did read some where that it is fine
My maxblock size is 450000 and max connection are set to 20 and i have both in and out connections with 9 peers attached.
So i am not changing a thing for now.
|
|
|
Thats exactly what happened to me. Very frustrating.
|
|
|
The block max size is set really high what do you recommend
I have seen on line 250000 to 1000000 size
Thats probably it.
|
|
|
I am not mergmining at all. But yes i could have something set wrong. Thats for sue this is my first setup. Where is the setting for merged or not will have to look for that.
|
|
|
I just updated all my s3 with the latest aug 2014 firware, and now the performance sucks. What are most s3 users doing to improve performance.
|
|
|
Jonny
The reason you were not able to connect i ;Ds because i had the firewall locked down to the subnet of my data center link. I was able to correct this. Our data center has us really bandwidth limited so i intend to get this resolved in the morning. Our latency from my office to there should be alot faster then it is currently.
I am in the process of building a new Debian box that I have placed in the data center so that should fix this issue..
Thanks so much for your input I greatly appreciate it.
|
|
|
|