Opened 8 years ago

Closed 8 years ago

#4612 closed enhancement (wontfix)

Put top-10 relays by bandwidth history back on metrics website

Reported by: karsten Owned by: karsten
Priority: Low Milestone:
Component: Metrics/Website Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I just removed the table listing the "top-10 relays by bandwidth history" from the metrics website in commit c7675d0. It was a list of relay fingerprints and written bytes in a given time frame. The list for September 1 to November 30, 2011 was:

Fingerprint Bandwidth history
24b1f63f7df9f85d711864811cc401be5eb5fb9a  103.92 TiB
7dcb5313b9541dd29c94bfde0adf91dc91d2cfe9  102.18 TiB
db8c6d8e0d51a42bdda81a9b8a735b41b2cf95d1  101.05 TiB
253dff1838a2b7782be7735f74e50090d46ca1bc  99.65 TiB
b93dcc053d7f0472bb17a4514e06fe76d9fb714b  98.17 TiB
6daa8317ba9ff4b4cad33588ad780ed65ba8af94  94.37 TiB
ff986a4573185a6912a0ff28335210cc05ce00de  74.14 TiB
2624ae0466bd02afaf3f263d4361d79abe0e7e05  72.84 TiB
4186509c707e96b77b51a76f8294d7e22ff52c61  62.36 TiB
2ffcceace86d8ca306d069386a65359bcee8d67a  61.50 TiB

The fingerprints were links to the relay pages showing more details. Also, there were input boxes for start and end date to customize the table content.

The reason why I took this list out is that updating this table for a new time interval took 2--5 minutes. That's unacceptable. This happened at least four times a day when the cached table data got stale or whenever a user entered a different start or end date of the time interval. This doesn't just delay page load times, but also keeps the database busy and affects other users.

If we want this table back, we'll have to pre-calculate some values.

I'm setting the priority to minor, because I don't think many people looked at this table at all.

Child Tickets

Change History (1)

comment:1 Changed 8 years ago by karsten

Resolution: wontfix
Status: newclosed

After some thinking I came to the conclusion that the table doesn't belong on the metrics website. We're in general not looking at single relays on the graphs pages, but only at aggregate statistics. The table would be better suited on Atlas or another Onionoo client. I opened #5430 to discuss whether this table is something to add to Atlas. If not, we can still add it to the Onionoo protocol, so that other Onionoo clients can display the data. Closing this ticket as wontfix.

Note: See TracTickets for help on using tickets.