[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #1841 [Metrics]: Node churn and uptime statistics
#1841: Node churn and uptime statistics
---------------------+------------------------------------------------------
Reporter: kjbbb | Owner: karsten
Type: task | Status: new
Priority: normal | Milestone:
Component: Metrics | Version:
Keywords: | Parent:
---------------------+------------------------------------------------------
I spent some time this summer designing a schema to support tracking of
relay uptime and churn statistics. The relay churn statistic should be
split up by platform, version, and guard/exit status for a more fine-tuned
insight into the network. The uptime statistic should be split into
guard/exit status and version, as it only sees individual platforms. Also,
the data the query returns currently is good for a time graph (similar to
Karsten's [https://trac.torproject.org/projects/tor/ticket/1721 Windows
relay uptime] graph), but it could be portrayed as a box-plot
distribution.
Relay churn is calculated from the unique routers from one week/month/year
that appear in the following week/month/year, and is relatively
straightforward to calculate. However, this query could use some
optimization because it takes a very long time to group individual routers
by the times they appear.
Relay uptime is more difficult to calculate with a database query because
"uptime sessions" need to be calculated in order to get a correct average.
This is near impossible to do with a database query, and must be done
programatically (with cursors in pl/pgsql or elsewhere).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1841>
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