Quote from: lumberjack on April 12, 2013, 11:07:41 PM

What I've noticed about 0.8.1 (and 0. Cool

when analyzing traffic with jnettop (was the quickest thing I had handy) is that a peer can ask for blocks and bitcoind will happily send them as fast as it possibly can. If that peer asks for a large range (500 at a time) bitcoind will happily saturate your entire uplink to deliver those block requests.

I've seen single peers pulling 250KB/sec through my DSL uplink, absolutely destroying anything else I'm trying to do. Restarting bitcoind disconnects that peer and they move onto another peer, which is why it seems stable again for a while after restarting. Eventually you get another greedy peer and the cycle repeats.

There is no built in throttling. You'll have to manually figure out a way to do QoS/throttling so it doesn't kill your link.

This behavior was in 0.7.x as well. See my post here: https://bitcointalk.org/index.php?topic=141802.0.

My observations are consistent with yours, which is why I tend NOT to run the client unless I need to move coins. Too often it ends up connecting to a peer that saturates my upload bandwidth and brings internet access to a standstill.

If you have a decent router, it should be possible to configure its QOS to limit bitcoind bandwidth. I have no need to run the client full-time, so I haven't bothered to take this step.