As discussed in the previous few pages, there are clearly some stratum issues still to resolve, and scalability issues to cope with ASIC sized workloads. BFL are sending (?have sent) forrestv a 5GH unit which should help drive development of both of these.

As discussed in the previous few pages, there are clearly some stratum issues still to resolve, and scalability issues to cope with ASIC sized workloads. BFL are sending (?have sent) forrestv a 5GH unit which should help drive development of both of these.

I've been mining on P2Pool for a week and I'm very impressed. I had a lot of problems with Phoenix originally but since switching to CGMiner all the stats are now good and I'm earning more than I ever did with 50BTC.

The only remaining issue is that the bitcoind getblocktemplate latency constantly increases over time in quite large jumps. It starts around 0.5s and creeps up slowly to around 2s then jumps to 10s and stays there.

Restarting everything: Bitcoin-qt, p2pool and CGMiner fixes it again but within 24 hours it'll be back up again.

I've been mining on P2Pool for a week and I'm very impressed. I had a lot of problems with Phoenix originally but since switching to CGMiner all the stats are now good and I'm earning more than I ever did with 50BTC.

The only remaining issue is that the bitcoind getblocktemplate latency constantly increases over time in quite large jumps. It starts around 0.5s and creeps up slowly to around 2s then jumps to 10s and stays there.

Restarting everything: Bitcoin-qt, p2pool and CGMiner fixes it again but within 24 hours it'll be back up again.

Anybody have any ideas what could be going on ?

Thanks

not sure about large jumps, but if your bitcoind is accepting transactions into memory that no pool will ever include then it'll gradually get slower

try bitcoind getmininginfo and see if it's much higher when it starts getting slow (or bitcoin-qt or whatever)

I've been mining on P2Pool for a week and I'm very impressed. I had a lot of problems with Phoenix originally but since switching to CGMiner all the stats are now good and I'm earning more than I ever did with 50BTC.

The only remaining issue is that the bitcoind getblocktemplate latency constantly increases over time in quite large jumps. It starts around 0.5s and creeps up slowly to around 2s then jumps to 10s and stays there.

Restarting everything: Bitcoin-qt, p2pool and CGMiner fixes it again but within 24 hours it'll be back up again.

I'm having an issue with p2pool and my router. It's not a show-stopper but I was wondering if someone might have an idea what's going on or be able to work with me to work out what is going on.

Basically, anytime I turn on QOS, I appear to stop doing any useful work. cgminer trundles along, fans spin, heat generated, Unfortunately, it appears that that's all wasted. the debug output of p2pool says that it's punishing shares for being stale. On the pools graph page, the incoming part of peers and the p2p in on traffic rate drop to zero. For whatever reason, it looks like peers are no longer supplying me with useful information (?)

I've even set things so that p2pool and bitcoind are QOSed to the highest speed category just in case they were getting squashed that way but it still gives the same result.

I can leave QOS off for now but I'd like to get this working properly. I'm using Tomato so the configuration is fairly straightforward and easy. I'll post some pictures in a little bit for illustration. I can perform packet captures and other good stuff but I'm not up on the p2pool networking.

I'm having an issue with p2pool and my router. It's not a show-stopper but I was wondering if someone might have an idea what's going on or be able to work with me to work out what is going on.

Basically, anytime I turn on QOS, I appear to stop doing any useful work. cgminer trundles along, fans spin, heat generated, Unfortunately, it appears that that's all wasted. the debug output of p2pool says that it's punishing shares for being stale. On the pools graph page, the incoming part of peers and the p2p in on traffic rate drop to zero. For whatever reason, it looks like peers are no longer supplying me with useful information (?)

I've even set things so that p2pool and bitcoind are QOSed to the highest speed category just in case they were getting squashed that way but it still gives the same result.

I can leave QOS off for now but I'd like to get this working properly. I'm using Tomato so the configuration is fairly straightforward and easy. I'll post some pictures in a little bit for illustration. I can perform packet captures and other good stuff but I'm not up on the p2pool networking.

the only thing i've ever used in windows that i've found did a proper job of managing bandwidth was netlimiter

I'm having an issue with p2pool and my router. It's not a show-stopper but I was wondering if someone might have an idea what's going on or be able to work with me to work out what is going on.

Basically, anytime I turn on QOS, I appear to stop doing any useful work. cgminer trundles along, fans spin, heat generated, Unfortunately, it appears that that's all wasted. the debug output of p2pool says that it's punishing shares for being stale. On the pools graph page, the incoming part of peers and the p2p in on traffic rate drop to zero. For whatever reason, it looks like peers are no longer supplying me with useful information (?)

I've even set things so that p2pool and bitcoind are QOSed to the highest speed category just in case they were getting squashed that way but it still gives the same result.

I can leave QOS off for now but I'd like to get this working properly. I'm using Tomato so the configuration is fairly straightforward and easy. I'll post some pictures in a little bit for illustration. I can perform packet captures and other good stuff but I'm not up on the p2pool networking.

the only thing i've ever used in windows that i've found did a proper job of managing bandwidth was netlimiter

I'm having an issue with p2pool and my router. It's not a show-stopper but I was wondering if someone might have an idea what's going on or be able to work with me to work out what is going on.

Basically, anytime I turn on QOS, I appear to stop doing any useful work. cgminer trundles along, fans spin, heat generated, Unfortunately, it appears that that's all wasted. the debug output of p2pool says that it's punishing shares for being stale. On the pools graph page, the incoming part of peers and the p2p in on traffic rate drop to zero. For whatever reason, it looks like peers are no longer supplying me with useful information (?)

I've even set things so that p2pool and bitcoind are QOSed to the highest speed category just in case they were getting squashed that way but it still gives the same result.

I can leave QOS off for now but I'd like to get this working properly. I'm using Tomato so the configuration is fairly straightforward and easy. I'll post some pictures in a little bit for illustration. I can perform packet captures and other good stuff but I'm not up on the p2pool networking.

the only thing i've ever used in windows that i've found did a proper job of managing bandwidth was netlimiter

In case anyone isn't familiar with Tomato, it is a specialized Linux distribution that runs on certain hardware routers.

Other connections appear to occur with no issues (unless I goof the configuration) and if I look in the details, I can see connections between external hosts and my own on the bitcoind and p2pool ports. I can't think it would be anything about Python that would be causing the issue. Hard to see what about QOS would be an issue since it's basically just prioritizing packets. But there must be more to it.

I'm having an issue with p2pool and my router. It's not a show-stopper but I was wondering if someone might have an idea what's going on or be able to work with me to work out what is going on.

Basically, anytime I turn on QOS, I appear to stop doing any useful work. cgminer trundles along, fans spin, heat generated, Unfortunately, it appears that that's all wasted. the debug output of p2pool says that it's punishing shares for being stale. On the pools graph page, the incoming part of peers and the p2p in on traffic rate drop to zero. For whatever reason, it looks like peers are no longer supplying me with useful information (?)

I've even set things so that p2pool and bitcoind are QOSed to the highest speed category just in case they were getting squashed that way but it still gives the same result.

I can leave QOS off for now but I'd like to get this working properly. I'm using Tomato so the configuration is fairly straightforward and easy. I'll post some pictures in a little bit for illustration. I can perform packet captures and other good stuff but I'm not up on the p2pool networking.

the only thing i've ever used in windows that i've found did a proper job of managing bandwidth was netlimiter

In case anyone isn't familiar with Tomato, it is a specialized Linux distribution that runs on certain hardware routers.

Other connections appear to occur with no issues (unless I goof the configuration) and if I look in the details, I can see connections between external hosts and my own on the bitcoind and p2pool ports. I can't think it would be anything about Python that would be causing the issue. Hard to see what about QOS would be an issue since it's basically just prioritizing packets. But there must be more to it.

Depends how Tomato handles QoS. You can block some traffic if you give higher priority and allow another to saturate your link. QoS isn't simple at all (you must define many compromises to make it work), if your tools make you think it is simple they probably do it wrong.

I'm having an issue with p2pool and my router. It's not a show-stopper but I was wondering if someone might have an idea what's going on or be able to work with me to work out what is going on.

Basically, anytime I turn on QOS, I appear to stop doing any useful work. cgminer trundles along, fans spin, heat generated, Unfortunately, it appears that that's all wasted. the debug output of p2pool says that it's punishing shares for being stale. On the pools graph page, the incoming part of peers and the p2p in on traffic rate drop to zero. For whatever reason, it looks like peers are no longer supplying me with useful information (?)

I've even set things so that p2pool and bitcoind are QOSed to the highest speed category just in case they were getting squashed that way but it still gives the same result.

I can leave QOS off for now but I'd like to get this working properly. I'm using Tomato so the configuration is fairly straightforward and easy. I'll post some pictures in a little bit for illustration. I can perform packet captures and other good stuff but I'm not up on the p2pool networking.

the only thing i've ever used in windows that i've found did a proper job of managing bandwidth was netlimiter

Nope. I have started to use blockmaxsize=5000 to see what will be changed. And so far there is no big difference.bitcoin-qt continues to increase RAM consumption even when new block is found.I can see on Graphs that when Bitcoin-qt releases occupied RAM then latency drops to its usual values.

2. With p2pool we are real miners and make our own blocks, so edit the important settings in your bitcoin.conf!

Code:

blockmaxsize=250000 # default: 250000

blockprioritysize=27000 # default: 27000

mintxfee=0.0002 # default: 0.0001

minrelaytxfee=0.0002 # default: 0.0001

Setting mintxfee and minrelaytxfee higher than default will increase your getblocktemplate latency. It's a matter of opinion, but I think those defaults are too low for the network, so, by increasing them a bit, you are also benefiting the network. I would personally recommend setting both to 0.0005.

Edit: what happens is that lots of free and low fee transactions accumulate on the mempool, which increases getblocktemplate latency, due to an algorithmic flaw of bitcoind's getblocktemplate. It might not matter for most pools, but p2pool is more dependant on this. Setting mintxfee/minrelaytxfee above default 0.0001 reduces the accumulation of mempool garbage. Restarting bitcoind also clears the mempool and helps for a short time.

2. With p2pool we are real miners and make our own blocks, so edit the important settings in your bitcoin.conf!

Code:

blockmaxsize=250000 # default: 250000

blockprioritysize=27000 # default: 27000

mintxfee=0.0002 # default: 0.0001

minrelaytxfee=0.0002 # default: 0.0001

Setting mintxfee and minrelaytxfee higher than default will increase your getblocktemplate latency. It's a matter of opinion, but I think those defaults are too low for the network, so, by increasing them a bit, you are also benefiting the network. I would personally recommend setting both to 0.0005.

Until bitcoind gets optimized, getblocktemplate just gets too slow with the default minrelaytxfee=0.0001.

Maybe this is hardware or environment related? I'm still using default settings and latest p2pool. My stale rate is always 10-15% less than the pool's rate. Yes, according to p2pool my bitcoind latency is at 10s. So what?

M

EDIT: I restarted bitcoind, it did significantly reduce getblocktemplate latency. Don't see a big deal here, have to restart things regularly anyhow. Just had to restart cgminer because it went funny on me. Presumably hit the AMD driver time limit.

I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!

2. With p2pool we are real miners and make our own blocks, so edit the important settings in your bitcoin.conf!

Code:

blockmaxsize=250000 # default: 250000

blockprioritysize=27000 # default: 27000

mintxfee=0.0002 # default: 0.0001

minrelaytxfee=0.0002 # default: 0.0001

Setting mintxfee and minrelaytxfee higher than default will increase your getblocktemplate latency. It's a matter of opinion, but I think those defaults are too low for the network, so, by increasing them a bit, you are also benefiting the network. I would personally recommend setting both to 0.0005.

Until bitcoind gets optimized, getblocktemplate just gets too slow with the default minrelaytxfee=0.0001.

Maybe this is hardware or environment related? I'm still using default settings and latest p2pool. My stale rate is always 10-15% less than the pool's rate. Yes, according to p2pool my bitcoind latency is at 10s. So what?

M

EDIT: I restarted bitcoind, it did significantly reduce getblocktemplate latency. Don't see a big deal here, have to restart things regularly anyhow. Just had to restart cgminer because it went funny on me. Presumably hit the AMD driver time limit.

I've been running with the blockmaxsize and mintxfee setting per above for the last 12 hours and it didn't seem to help. I just added in the blockprioritysize and minrelaytxfee settings and it looks to have made a huge difference.