Opened 11 years ago

Last modified 7 years ago

#802 closed defect (Not a bug)

BandwidthBurst rate being used constantly

Reported by: micah Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.1.4-alpha
Severity: Keywords:
Cc: micah, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I have three machines, all configured exactly the same way acting as round-robin web servers. They get an even distribution
of traffic, averaging 50kbps in and 200kbps out and have had an even distribution amongst the nodes for a year and a half.

I installed tor on one of the nodes to test an exit enclave setup, with the idea that if it worked well, I would deploy it
to the other nodes (as well as elsewhere). I used the following configuration:

SocksPort 0 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost
Log notice syslog
RunAsDaemon 1
DataDirectory /var/lib/tor
Nickname auk
Address my.ip.here
OutboundBindAddress my.ip.here
ContactInfo my.contact.info.here
ORPort 9001
ExitPolicyRejectPrivate 0
ExitPolicy accept my.ip.here:80
ExitPolicy accept my.ip.here:443
ExitPolicy reject *:*
BandwidthRate 250 KB
BandwidthBurst 1MB

As you can see, I set BandwidthBurst to 1MB, and BadwidthRate to be 250KB, but looking at my bandwidth usage
statistics, I see that this node is using 1MB the entire time, averaging 872kbps in and 1.03M out (almost always at
this rate, with some fluctuations up to 2.35M in and 2.71M out.

This doesn't seem like what I would expect for these bandwidth settings, I could be misunderstanding how these
are applied, and if so please tell me what I am missing.

Thanks for your work on tor, its appreciated!

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (5)

comment:1 Changed 11 years ago by arma

Hi Micah,

Are you confusing bytes per second with bits per second?

Tor always uses bytes per second.

From looking at auk's bandwidth lines now:
bandwidth 131072 524288 186301
it looks like it should be behaving roughly appropriately. See also

http://trunk.torstatus.kgprog.com/router_detail.php?FP=7661e748639a0a31ffc49380ac19bfd53ad2a8ae

comment:2 Changed 11 years ago by micah

Hi Roger,

Thanks for the response, and the link to the torstatus page, that is really useful!

Are you confusing bytes per second with bits per second?
Tor always uses bytes per second.

I think I may be, as my normal bandwidth measurements are done in bits/sec, so let me re-do this in bytes/sec: my average bandwidth on these servers, without tor, is between 6.25KB/s - 25KB/s, when I setup tor with BandwidthRate set to 250KB/s and BandwidthBurst set to 1MB I was seeing between 109KB/s and 131.8KB/s with fluctuations up to 300.8KB/s in and 346.9KB/s out. Which seems within the rates that were set.

From looking at auk's bandwidth lines now:
bandwidth 131072 524288 186301
it looks like it should be behaving roughly appropriately. See also

Actually, since reporting this bug I've adjusted the bandwidth configuration to be:

BandwidthRate 250 KB
BandwidthBurst 1MB
RelayBandwidthRate 128KB
RelayBandwidthBurst 512KB

Looking at the reported bandwidth from the torstatus page, the numbers match exactly the RelayBandwidthRate and RelayBandwidthBurst rates, which is expected because there is nobody using the node as its intended purpose as an exit enclave right now, so it is only acting as a middle router, pushing tor bytes through the network.

Sorry for the units screw up, I believe that this can be closed now.

comment:3 Changed 11 years ago by arma

Great. Closing.

comment:4 Changed 11 years ago by arma

flyspray2trac: bug closed.

comment:5 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.