[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #6498 [Metrics Website]: new metrics graph showing number of 100mbit exits
#6498: new metrics graph showing number of 100mbit exits
-----------------------------+----------------------------------------------
Reporter: arma | Owner:
Type: project | Status: needs_information
Priority: normal | Milestone:
Component: Metrics Website | Version:
Keywords: SponsorJ | Parent:
Points: | Actualpoints:
-----------------------------+----------------------------------------------
Changes (by gsathya):
* status: needs_revision => needs_information
Comment:
Replying to [comment:13 karsten]:
> Replying to [comment:10 karsten]:
> Your current code has two problems:
> - It only considers a relay as almost fast if it meets the relaxed
bandwidth requirements but fails the original bandwidth requirements. In
numbers, 80 < rate < 95 and 2000 < advertised < 5000. If a relay has a
rate of 90 and advertises 6000, you wouldn't list it.
Oh. I thought an almost-fast-exit relay should satisfy *both* -
1) 80 < rate < 95 and
2) 2000< advertised < 5000.
Sorry. So, it should be "80 < rate < 95 *or* 2000 < advertised < 5000"? Is
this correct?
{{{
if not ((80 * 125 * 1024 <= relay.get('bandwidth_rate', -1) <= 95 *
125 * 1024) or (2000 * 1024 <= relay.get('advertised_bandwidth', -1) <=
5000 * 1024)):
continue
}}}
> - Once you rewrite the bandwidth requirements, you'll also want to
rewrite the port requirement to check if all four ports are permitted. If
a relay has rate >= 95 and advertised >= 5000, and supports all four ports
(of which you only check two), you'd call it an almost fast exit, though
it's in fact a fast exit.
Ok.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6498#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