[metrics-bugs] #8127 [Metrics/Website]: Bring back the relays-by-country graph

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Jan 14 09:56:42 UTC 2019


#8127: Bring back the relays-by-country graph
-----------------------------+------------------------------
 Reporter:  karsten          |          Owner:  metrics-team
     Type:  enhancement      |         Status:  assigned
 Priority:  Low              |      Milestone:
Component:  Metrics/Website  |        Version:
 Severity:  Normal           |     Resolution:
 Keywords:                   |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:                   |        Sponsor:
-----------------------------+------------------------------

Comment (by anadahz):

 Replying to [comment:4 karsten]:
 > Replying to [comment:3 anadahz]:
 > > What kind of resources are required?
 > >
 > > Can a dedicated server allocated only to do this task help to bring
 back the relays-by-country graphs?
 >
 > Unfortunately, it's not just a question of hardware. The code used for
 the blog post is good enough to run it once for a blog post, but it needs
 more work for being run periodically. Here are a few issues:
 >
 >  - Every time this code runs, it processes *all* descriptors in the in/
 directory. In a production environment we'd want it to skip descriptors it
 has processed before and use previously processed aggregations from them.
 >
 >  - Updating geoip files is a manual steps. In fact, we're currently
 using the very same geoip file in a graph covering years of data. We'll
 need to find a way for automating updating geoip files. And we need to
 define which geoip file we're using for any given consensus. That last
 sentence alone is far from being trivial if we want to ensure that two
 people have a chance to independently produce the same graph.

 Aren't these the same GeoIP files as the ones used for Tor metrics
 currently?
 >
 >  - Everything here works with files, but we'll want to use a database,
 or we'll be sad whenever the server reboots in the wrong moment. And we
 want the database schema to scale for the next five years.

 Nonetheless do you think that these issues can be created as separate sub-
 tickets?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8127#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the metrics-bugs mailing list