Topic: Bitcoin client upload saturating my DSL connection. (No bandwidth throttling ?) (Read 12751 times)
June 15, 2014, 04:12:51 AM
Bitcoin client downloaded data is too large, it is a hassle.
June 02, 2014, 12:22:36 PM
Give the drop in number of nodes I think this might be a reason / solution.
February 18, 2013, 09:46:59 AM
In linux you can use a tool called "trickle" to limit your bandwidth like this:
That will limit its upload to 50kb/s
Code:
trickle -u50 bitcoind
That will limit its upload to 50kb/s
So useful even now, half year later, I dug this from google. Thanks!
Is there anything equivalent to trickle for cpu usage?
February 17, 2013, 11:30:02 AM
In linux you can use a tool called "trickle" to limit your bandwidth like this:
That will limit its upload to 50kb/s
Code:
trickle -u50 bitcoind
That will limit its upload to 50kb/s
So useful even now, half year later, I dug this from google. Thanks!
Is there anything equivalent to trickle for cpu usage?
January 11, 2013, 06:53:46 AM
In linux you can use a tool called "trickle" to limit your bandwidth like this:
That will limit its upload to 50kb/s
Code:
trickle -u50 bitcoind
That will limit its upload to 50kb/s
So useful even now, half year later, I dug this from google. Thanks!
Is there anything equivalent to trickle for cpu usage?
$ man nice
January 11, 2013, 06:50:16 AM
In linux you can use a tool called "trickle" to limit your bandwidth like this:
That will limit its upload to 50kb/s
Code:
trickle -u50 bitcoind
That will limit its upload to 50kb/s
So useful even now, half year later, I dug this from google. Thanks!
Is there anything equivalent to trickle for cpu usage?
January 11, 2013, 05:37:05 AM
In linux you can use a tool called "trickle" to limit your bandwidth like this:
That will limit its upload to 50kb/s
Code:
trickle -u50 bitcoind
That will limit its upload to 50kb/s
So useful even now, half year later, I dug this from google. Thanks!
October 24, 2012, 06:12:01 PM
If You are behind NAT then don't open incoming 8333 port (disable UPnP in bitcoin settings) and bitcoin will connect to max of 8 nodes. Just that simple, just that clean!
Thanks all for your numerous "Just that simple" solution.If you haven't noticed, I'm inquiring about a solution for the general public.
The general public has their bitcoin client behind a NAT without a forwarded port and therefore only 8 connections. Those who know how to open a port know who to limit the bandwidth using an external program.
But it would be neater to have it integrated in the client itself.
Quote
use netlimiter
Net Limiter occupies NDIS driver interface and introduces additional problems.you can disable/enable the netlimiter drivers at will
October 24, 2012, 02:18:35 PM
If You are behind NAT then don't open incoming 8333 port (disable UPnP in bitcoin settings) and bitcoin will connect to max of 8 nodes. Just that simple, just that clean!
Thanks all for your numerous "Just that simple" solution.If you haven't noticed, I'm inquiring about a solution for the general public.
Can you answer to this guy's problem two post up ?
I've noticed too that bitcoind is saturating my upload speed, and I don't even have port forwarding from my gateway linux machine to the 'internal' linux server where I have bitcoind running.
Seems pretty poor design to not have it in the client already to limit upload bandwidth like bittorrent etc. has done for YEARS.
...
Seems pretty poor design to not have it in the client already to limit upload bandwidth like bittorrent etc. has done for YEARS.
...
October 24, 2012, 02:10:48 PM
If You are behind NAT then don't open incoming 8333 port (disable UPnP in bitcoin settings) and bitcoin will connect to max of 8 nodes. Just that simple, just that clean!
Thanks all for your numerous "Just that simple" solution.If you haven't noticed, I'm inquiring about a solution for the general public.
The general public has their bitcoin client behind a NAT without a forwarded port and therefore only 8 connections. Those who know how to open a port know who to limit the bandwidth using an external program.
But it would be neater to have it integrated in the client itself.
Quote
use netlimiter
Net Limiter occupies NDIS driver interface and introduces additional problems. October 24, 2012, 10:17:56 AM
If You are behind NAT then don't open incoming 8333 port (disable UPnP in bitcoin settings) and bitcoin will connect to max of 8 nodes. Just that simple, just that clean!
Thanks all for your numerous "Just that simple" solution.If you haven't noticed, I'm inquiring about a solution for the general public.
The general public has their bitcoin client behind a NAT without a forwarded port and therefore only 8 connections. Those who know how to open a port know who to limit the bandwidth using an external program.
But it would be neater to have it integrated in the client itself.
like i said a month or so ago in this thread, i use netlimiter
there are also free utilities that will do the same thing for windows
or you can use the QoS that comes with windows, I believe.. or should at least be on your router/DSL modem/whatever
October 24, 2012, 09:08:23 AM
If You are behind NAT then don't open incoming 8333 port (disable UPnP in bitcoin settings) and bitcoin will connect to max of 8 nodes. Just that simple, just that clean!
Thanks all for your numerous "Just that simple" solution.If you haven't noticed, I'm inquiring about a solution for the general public.
The general public has their bitcoin client behind a NAT without a forwarded port and therefore only 8 connections. Those who know how to open a port know who to limit the bandwidth using an external program.
But it would be neater to have it integrated in the client itself.
October 23, 2012, 08:55:21 PM
1. Multi-homed machine; Bitcoin has it's own IP address
2. HTB to throttle bandwidth on that interface or configure your gateway to limit it's bandwidth.
2. HTB to throttle bandwidth on that interface or configure your gateway to limit it's bandwidth.
October 23, 2012, 01:38:12 PM
In linux you can use a tool called "trickle" to limit your bandwidth like this:
That will limit its upload to 50kb/s
You rock! This is exactly what I need.Code:
trickle -u50 bitcoind
That will limit its upload to 50kb/s
EDIT: Looks like trickle only supports dynamically linked executables. Looks like my bitcoin-qt is statically linked:
Code:
rune@rune-desktop:~$ ldd /usr/bin/bitcoind
not a dynamic executable
not a dynamic executable
I'm using the PPA version (0.7.0-precise1). Which version are you using?
In linux you can use a tool called "trickle" to limit your bandwidth like this:
That will limit its upload to 50kb/s
Sorry but what about adding a way to set connection limiting setting of bitcoin.conf to the UI ?Code:
trickle -u50 bitcoind
That will limit its upload to 50kb/s
This is ridiculously weird.
And NO I am not editing my conf file nor am I going to install Linux for this.
Thanks HeavyMetal for trying to help
October 22, 2012, 09:52:28 PM
If You are behind NAT then don't open incoming 8333 port (disable UPnP in bitcoin settings) and bitcoin will connect to max of 8 nodes. Just that simple, just that clean!
Thanks all for your numerous "Just that simple" solution.If you haven't noticed, I'm inquiring about a solution for the general public.
Can you answer to this guy's problem two post up ?
I've noticed too that bitcoind is saturating my upload speed, and I don't even have port forwarding from my gateway linux machine to the 'internal' linux server where I have bitcoind running.
Seems pretty poor design to not have it in the client already to limit upload bandwidth like bittorrent etc. has done for YEARS.
...
Seems pretty poor design to not have it in the client already to limit upload bandwidth like bittorrent etc. has done for YEARS.
...
October 22, 2012, 08:46:17 PM
If You are behind NAT then don't open incoming 8333 port (disable UPnP in bitcoin settings) and bitcoin will connect to max of 8 nodes. Just that simple, just that clean!
October 22, 2012, 11:29:57 AM
There has to been numerous speed limiting algorithm developed for eMule and uTorrent.
Here's more. :
http://bittorrent.org/beps/bep_0029.html
http://tools.ietf.org/html/draft-ietf-ledbat-congestion-00
Here's more. :
http://bittorrent.org/beps/bep_0029.html
http://tools.ietf.org/html/draft-ietf-ledbat-congestion-00
Quote
...μTP eliminates this problem by being better at only using bandwidth when there is no other traffic competing, and automatically slowing or stopping BitTorrent transfers before network connections seize up.
...
It does this by being able to detect congestion on a network based on how long a packet takes to be sent from one peer to the next. If things start to take longer, then μTP adjusts the rate of sending accordingly....
...
It does this by being able to detect congestion on a network based on how long a packet takes to be sent from one peer to the next. If things start to take longer, then μTP adjusts the rate of sending accordingly....
September 21, 2012, 06:06:05 PM
Trying 'trickled' and then 'trickle' for the process. More often that not bitcoin will run for a bit and then die. Looking at 'bitcoind getinfo' shows that it has no connections. It seems to try to find connections and then exits. namecoind exits really very quickly.
Anyone else have luck with the 'trickle' traffic shaper?
UpdatE: Also noticed that bitcoind doesn't keep synchronized to the network, even though it shows as having connections, when run via 'trickle'. If I run it normally, it synchronizes just fine.
Anyone else have luck with the 'trickle' traffic shaper?
UpdatE: Also noticed that bitcoind doesn't keep synchronized to the network, even though it shows as having connections, when run via 'trickle'. If I run it normally, it synchronizes just fine.
September 21, 2012, 03:59:25 PM
I've noticed too that bitcoind is saturating my upload speed, and I don't even have port forwarding from my gateway linux machine to the 'internal' linux server where I have bitcoind running.
Seems pretty poor design to not have it in the client already to limit upload bandwidth like bittorrent etc. has done for YEARS.
Got to try 'trickle', that might work well.
Seems pretty poor design to not have it in the client already to limit upload bandwidth like bittorrent etc. has done for YEARS.
Got to try 'trickle', that might work well.
August 28, 2012, 06:53:46 PM
Start with the command line option -maxconnections=X, where X is the largest number of other peers you want to maintain connections with. This won't prevent one of the clients wanting to get the whole blockchain from you, but it will lower the chance.
Jump to: