New fast p2pool node.
Address:
http://hostv.pl:9332/Location
Roubaix, Francja (OVH Datacenter RBX)
Server: core i7 @ 3.2GHz, 16GB Ram , 2x2TB SATA
Connection: 1Gbps
If someone want I can add support for ipv6
Fee: 0.5% but I will change to 0.0% after new release p2pool
p2pool updatet to 9.0-dirty
bitcoind v0.7.1-154-ge12efb9-dirty-beta
Get work latency
less than 0.1s ( 0.0546s avg)
the more transactions you are carrying, the higher the latency is
when i have 2000 transactions waiting, it gets to around .4s, when i have 100 transactions, it's like .02s
not rly a fair measurement, since *generally* the more transactions you have, the more tx fees you get... (notwithstanding accepting a lot of 0 fee transactions)
person X might have a .2s latency, but be mining towards 25.5 payout, person Y might have .1 but be mining towards 25.1
surely there's a better way to graph that data, like a graph that shows the latency as well as the current block size.
in the grand scheme of things, 100 or 200 ms isn't going to kill you. it's how slow the shares spread on the p2p network. mostly caused by the extremely small # of outgoing connections.
it's a wise move to edit the source to allow more than 10 outgoing, barring a connection via a modem or ISDN
in fact, i think sometime in the next hour or so, i'll start up a p2pool node with 100 or 200 outgoing connections and just see if it lowers the entire network orphan rate
