[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Full bandwidth is not used.



Unfortunately the state doesn't provide a complete bandwidth history - if you check on line 1168 of src/or/rephist.c you'll see:

/** How many bandwidth usage intervals do we remember? (derived) */
#define NUM_TOTALS (NUM_SECS_BW_SUM_IS_VALID/NUM_SECS_BW_SUM_INTERVAL)

This is used later when writing to the state (line 1441 of the same file) - honestly I'm green enough with C that I got lost pretty quick once it started juggling smart lists and buffers around but I'll take the comments at their word ;)

This is why I don't use it to populate past bandwidth data in arm. Cheers! -Damian

On Sun, Mar 7, 2010 at 3:16 AM, Paul Menzel <paulepanter@xxxxxxxxxxxxxxxxxxxxx> wrote:
Am Freitag, den 05.03.2010, 23:54 +0100 schrieb Paul Menzel:
> Am Freitag, den 05.03.2010, 10:17 -0500 schrieb andrew@xxxxxxxxxxxxxx:
> > On Fri, Mar 05, 2010 at 09:32:59AM +0100, paulepanter@xxxxxxxxxxxxxxxxxxxxx wrote 1.4K bytes in 39 lines about:
> > : > What did you configure for your bandwidth limits or accountingmax?
> > :
> > : I did not configure them and so the defaults are used. arm is displaying
> > : »(cap: 5 MB, burst: 10 MB)«.
> >
> > Ok, then Tor will figure out how much bandwidth it can reliably provide.
>
> On what conditions does that depend?
>
> > If you look at your (datadirectory)/state file, it will show you how
> > much bandwidth tor has been providing over time.
>
> I guess arm is using this or something similar to display the bandwidth
> usage of Tor.

On average arm’s values are the same as the ones in
`(datadirectory)/state`.

[…]


Thanks,

Paul