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

Re: [tor-bugs] #9301 [arm]: add advertised bandwidth

#9301: add advertised bandwidth
-----------------------+----------------------------------------------------
    Reporter:  hsn     |       Owner:  atagar  
        Type:  task    |      Status:  reopened
    Priority:  normal  |   Milestone:          
   Component:  arm     |     Version:          
  Resolution:          |    Keywords:          
      Parent:          |      Points:          
Actualpoints:          |  
-----------------------+----------------------------------------------------

Comment(by hsn):

 I checked onionoo data directly. You seems to be right with your atlas
 formula, there is one huge difference between onionoo data and torstatus
 data:

 torstatus
 Bandwidth (Max/Burst/__Observed__ - In Bps):         1073741824 /
 1073741824 / __7031__

 oo
 "bandwidth_rate":1073741824,
 "bandwidth_burst":1073741824,
 "observed_bandwidth":368035,
 "advertised_bandwidth":368035,

 torstatus shows real traffic reported by relay in __observed_bandwidth__,
 oo shows value assigned by bw authority based on bw weight assigned. If i
 look into ''cached-descriptors'' then torstatus report value from this
 file. Value "observed_bandwidth" from oo can not be found in any cached*
 file. since its new relay it never had that much traffic.

 So question is where onionoo observed_bandwidth comes from?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9301#comment:14>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs