When I was running my local node, my bitcoind had 1 maxconnection, listen=0, and connected to my germany server.  p2pool had 6 outgoing and default incoming.  i don't think i ever ended up with more than 10 incoming though.  i shut it down after a day since I was still getting around 1-2% DOA, but also about 10-15% orphans...  which was more than the typical 5% DOA and 3% orphans or so I got mining to my remote server.

I think if I tried it again it would be with the 1 bitcoind connection and 3 p2pool connections, one to my server in germany, one to my server in jacksonville, and one to my friend's server in quebec.  i suspect this would cut the # of orphans, maybe down to 10% or so...    this assumption for when my link is performing fine 24/7 instead of when bandwidth is oversold like it is now

I restarted server roughly 3 1/2 hrs ago, at 4:40PM local time,

here is what my link has been like since then (I started the ping about 30 minutes before restarting the server):



it is scaled to 400ms and 10% packetloss.  the top bar is jitter (scaled to 50ms, goes off the chart a lot).  note that this is a ping to my first hop, so to get the ping times to my server, add 150ms to that

in this time the server has gotten 29 shares, 0 orphans, 4 DOA.  17 of those are mine, and 2 of the DOA are mine.  12 are others, and 2 of the DOA are them (1G8D has gotten incredibly unlucky with 2 DOA out of 8 shares, even though it looks like his DOA rate is only about 3% to server)

anyway, even my 11.5% DOA or so would have an efficiency of well over 100%,  with that ^^ crap link shown above

there's a 7970 for $318 after rebates + the games bundle, which would make it like $295 or so

http://slickdeals.net/permadeal/97540/tigerdirect-sapphire-radeon-hd-7970-3gb-384bit-gddr5-overclocked-pci-express-3.0-video-card-amd-4game-bundle-coupons

the newegg one was slightly cheaper but it's out of stock now

sapphire 7950 is $260, still live

http://slickdeals.net/f/6105062-Sapphire-Radeon-HD-7950-3GB-GDDR5-PCI-Express-Video-Card-Crysis-3-Tomb-Raider-BioShock-Infinite-Far-Cry-3-Blood-Dragon-259-99-after-Rebate-Free-Shipping

powercolor 7950 open box $209 + $3 shipping

http://www.newegg.com/Product/Product.aspx?Item=N82E16814131478R

(haha, nm, that one just went out of stock)

my powercolor has one fan and it's easy to cool

i guess maybe if youre mining useless scrypt shit?

btw thanks for the heads up, that's one of those profit when it hits your doorstep items

though i wouldnt mine with it, so you could still sell it as 'new in box'

That's BS.  

Plenty of people have bought stuff for mining and either never cared about making a profit or were incredibly naive

but you need to redo your calculations in any case


then you'd buy it for market price, not usb trash or 5ghash garbage

i think everyone that participates should receive 100 devcoins

Well, just three 6990's left now, the 5970 got sold.  If you're really interested, PM me.. I forgot about this thread =p

So they could have given you 2x Xeon L7455?

*scratch*

nah, he's a major contributor to p2pool.  i think he's been mining it for years.   i'm just whining and wish he had a faster setup.  =p

I don't even know what IP he mines to, which I guess is part of the problem.  I think he's on a private node, probably with just 6 outgoing connections.

oh, I know it was that address since my orphan showed up in the 'headers' list... then I go to the parent share and click on child, and it shows what replaced your orphaned share (if it works the way I think it does, that replacement is actually dictated by the share that comes after it)

Isn't all that's required the base latency of the jalapeno?  How do they work?  Does it do work for 2s then spit out results?  1s?  1000ms should result in 10% DOA.

The orphans shouldnt deviate from what you'd get from using a GPU

i guess i should also mention that 50% of them are orphaned by

1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe

and i know he isnt using an asic, so why so slow?

do you have to use stratum?   it has some 1/2 second delay or so for me

it looks like whatever you're using has 1500-2000ms latency.  so we'll be optimistic and consider that 15% DOA.     now, can you set up your pool so you have 5% or less orphans?  probably not with 6 outgoing connections and 0 incoming

i don't understand why people run pools locally when they'd be better off using a remote server.  i ran mine locally for about 2 days

not 7970's or 6990's.  

and if you pay 11c/kWh, why even be considering it?

i pay a little over 6 cents and make about $40 per ghash (per month), before including equipment depreciation and the value of my time

in about a week, that'll be 20-25% less

the 'best gpu mining setup', you wouldnt even take the cards out of the box.  you'd do rebates and sell some games, then resell the card as new in box on ebay.

interesting

here, what i posted on june 16th:

It'll go up 20%, 25% or more for the next few cycles.  Then eventually the hobbyists will stop spending all their excess cash and the difficulty level won't increase as much.

all the prices for ASICs and such I have seen lately are ludicrous

but I applaud the business savvy of those folks that have sold/are selling their avalon 2's atm

wtf thinking it would stay at 19m?

obvious sell, while there are still suckers out there that don't understand how difficulty works, and/or hobbyists with too much money on their hands

difficulty - it did just what i said it would, dropped for a few days (ppl taking GPUs offline) then jumped back up, as a bunch of fools bring their... err, well, things like that Jalapeno online.  it's boggling to me how someone would pay $2000 for one of those

more like asicminer selling bitcoins as soon as they get them.  wouldn't doubt a majority of the people that are wasting money on these crap devices that asicminer has made available (good lord, i wonder why?) trying to recover money in a futile effort

Oh, I guess there's also the case where my client reported one of my shares as dead right after a block was solved, but then later it, uh, became undead the next work cycle.  I guess it's the same phenomenon?

6.8%
9.6%
6.6%
16.7%

haha, that's a lot more unlikely than not finding one at all for 4 days =p  (looking at the last 4)

OK, so I've been looking at my orphans for the last 10 days or so.... about 33% of them occur after a block solve.

Here's another example (editing out the multiple new work for workers messages, so there's just the one)

2013-06-21 22:31:58.822054 P2Pool: 17355 shares in chain (17359 verified/17359 total) Peers: 77 (16 incoming)
2013-06-21 22:31:58.822116  Local: 6968MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-6%) Expected time to share: 11.7 minutes
2013-06-21 22:31:58.822136  Shares: 128 (2 orphan, 7 dead) Stale rate: ~7.0% (3-13%) Efficiency: ~107.9% (101-112%) Current payout: 0.2439 BTC
2013-06-21 22:31:58.822159  Pool: 582GH/s Stale rate: 13.9% Expected time to block: 1.6 days
2013-06-21 22:32:03.229133 Skipping from block 2d6aa3455150dc4ed11205a84269ec9d8248c74fba1760ca6c to block 35054271c485c0c1e7d0581d22196ef7a11b00ab308c9a20ad!
2013-06-21 22:32:03.273201 New work for worker! Difficulty: 15.000000 Share difficulty: 11481.054517 Total block value: 25.000000 BTC including 0 transactions
2013-06-21 22:32:03.873304 Punishing share for 'Block-stale detected! 2d6aa3455150dc4ed11205a84269ec9d8248c74fba1760ca6c < 35054271c485c0c1e7d0581d22196ef7a11b00ab308c9a20ad'! Jumping from ab17a876 to f4ee4862!
2013-06-21 22:32:04.180605 New work for worker! Difficulty: 15.000000 Share difficulty: 11414.202197 Total block value: 25.002500 BTC including 4 transactions
2013-06-21 22:32:05.143761 Punishing share for 'Block-stale detected! 2d6aa3455150dc4ed11205a84269ec9d8248c74fba1760ca6c < 35054271c485c0c1e7d0581d22196ef7a11b00ab308c9a20ad'! Jumping from ab17a876 to f4ee4862!
2013-06-21 22:32:05.146830 Punishing share for 'Block-stale detected! 2d6aa3455150dc4ed11205a84269ec9d8248c74fba1760ca6c < 35054271c485c0c1e7d0581d22196ef7a11b00ab308c9a20ad'! Jumping from ab17a876 to f4ee4862!
2013-06-21 22:32:06.846943 P2Pool: 17354 shares in chain (17359 verified/17359 total) Peers: 77 (16 incoming)
2013-06-21 22:32:06.847025  Local: 7054MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-6%) Expected time to share: 11.5 minutes
2013-06-21 22:32:06.847051  Shares: 128 (2 orphan, 7 dead) Stale rate: ~7.0% (3-13%) Efficiency: ~107.7% (100-112%) Current payout: 0.2428 BTC
2013-06-21 22:32:06.847077  Pool: 581GH/s Stale rate: 13.7% Expected time to block: 1.7 days
2013-06-21 22:32:10.143508 Punishing share for 'Block-stale detected! 2d6aa3455150dc4ed11205a84269ec9d8248c74fba1760ca6c < 35054271c485c0c1e7d0581d22196ef7a11b00ab308c9a20ad'! Jumping from ab17a876 to f4ee4862!
2013-06-21 22:32:10.146594 Punishing share for 'Block-stale detected! 2d6aa3455150dc4ed11205a84269ec9d8248c74fba1760ca6c < 35054271c485c0c1e7d0581d22196ef7a11b00ab308c9a20ad'! Jumping from ab17a876 to f4ee4862!
2013-06-21 22:32:13.344146 New work for worker! Difficulty: 15.000000 Share difficulty: 11376.680741 Total block value: 25.002500 BTC including 4 transactions
2013-06-21 22:32:14.824266 New work for worker! Difficulty: 15.000000 Share difficulty: 11379.604632 Total block value: 25.002500 BTC including 4 transactions
2013-06-21 22:32:14.863067 P2Pool: 17356 shares in chain (17361 verified/17361 total) Peers: 77 (16 incoming)
2013-06-21 22:32:14.863146  Local: 6995MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-6%) Expected time to share: 11.6 minutes
2013-06-21 22:32:14.863172  Shares: 128 (2 orphan, 7 dead) Stale rate: ~7.0% (3-13%) Efficiency: ~107.9% (101-112%) Current payout: 0.2428 BTC
2013-06-21 22:32:14.863199  Pool: 576GH/s Stale rate: 13.9% Expected time to block: 1.7 days
2013-06-21 22:32:15.729087 New work for worker! Difficulty: 15.000000 Share difficulty: 11319.620580 Total block value: 25.002500 BTC including 4 transactions
2013-06-21 22:32:17.027868 GOT SHARE! Drizztztzzztztzzzzztzz f3db321a prev 15a3746e age 1.30s
2013-06-21 22:32:17.139592 New work for worker! Difficulty: 15.000000 Share difficulty: 11282.391344 Total block value: 25.002500 BTC including 4 transactions
2013-06-21 22:32:22.883715 P2Pool: 17350 shares in chain (17354 verified/17354 total) Peers: 77 (16 incoming)
2013-06-21 22:32:22.883792  Local: 7138MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-6%) Expected time to share: 11.4 minutes
2013-06-21 22:32:22.883817  Shares: 129 (2 orphan, 7 dead) Stale rate: ~7.0% (3-13%) Efficiency: ~108.3% (101-113%) Current payout: 0.2716 BTC
2013-06-21 22:32:22.883853  Pool: 591GH/s Stale rate: 14.1% Expected time to block: 1.6 days
2013-06-21 22:32:27.267897 New work for worker! Difficulty: 15.000000 Share difficulty: 11282.391344 Total block value: 25.001000 BTC including 2 transactions
2013-06-21 22:32:30.904216 P2Pool: 17350 shares in chain (17354 verified/17354 total) Peers: 77 (16 incoming)
2013-06-21 22:32:30.904297  Local: 6936MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-6%) Expected time to share: 11.7 minutes
2013-06-21 22:32:30.904323  Shares: 129 (2 orphan, 7 dead) Stale rate: ~7.0% (3-13%) Efficiency: ~108.3% (101-113%) Current payout: 0.2716 BTC
2013-06-21 22:32:30.904352  Pool: 591GH/s Stale rate: 14.1% Expected time to block: 1.6 days
2013-06-21 22:32:33.207259 New work for worker! Difficulty: 15.000000 Share difficulty: 11301.302403 Total block value: 25.001000 BTC including 2 transactions
2013-06-21 22:32:38.925707 P2Pool: 17327 shares in chain (17332 verified/17332 total) Peers: 77 (16 incoming)
2013-06-21 22:32:38.925789  Local: 6976MH/s in last 10.0 minutes Local dead on arrival: ~2.0% (0-6%) Expected time to share: 11.5 minutes
2013-06-21 22:32:38.925825  Shares: 129 (3 orphan, 7 dead) Stale rate: ~7.8% (4-14%) Efficiency: ~107.4% (100-112%) Current payout: 0.2428 BTC
2013-06-21 22:32:38.925861  Pool: 574GH/s Stale rate: 14.1% Expected time to block: 1.7 days

Here's what it looks like on a server in Canada's OVH datacenter (100ms from my Hetzner server):

My share:

Time first seen: Fri Jun 21 2013 22:32:17 GMT-0500 (Central Daylight Time) (1371871937.19677)
Peer first received from: 5.9.24.81,37483

The one that replaced it:

Time first seen: Fri Jun 21 2013 22:32:31 GMT-0500 (Central Daylight Time) (1371871951.30414)
Peer first received from: xxx,55412

Since there was one other 'new work' thing in there, it means that a 2nd share built off my own and that 2-share chain wasn't invalidated until the 3rd share.

For this to happen, that would mean that three clients would have had to accept one of the shares that my node 'punished' for being invalid (probably the one that came 600ms after the block was detected)...

or is my logic here wrong somewhere?

ed: edited out a 3rd party IP

ed2:  and here's the "offending" block:

http://blockchain.info/block/000000000000008f0ea3c9b07b3284ffdaad5b0dd31997ea1d02742bc9a185cb

blockchain.info reports it being first seen from my IP, 5.9.24.81

hmm..  or, it could be the one before it,

http://blockchain.info/block-index/394345

where it lists 5.9.24.81 as 10th or so

i think that one is probably the one.   the other came @ 32:27....  which would be 4 seconds before the share that replaced mine, but 26 seconds after the last block...  and would also mean that p2pool x's and p2pool y's were working off of different chains for at least those 26 seconds

that was someone's post on the quoted link (https://bitcointalk.org/index.php?topic=90658.msg998190#msg998190)  from june 2012