Opened 21 months ago

Closed 15 months ago

Last modified 15 months ago

#2105 closed enhancement (wontfix)

Add bandwidth tiers to NetDB overview

Reported by: Reportage Owned by: str4d
Priority: minor Milestone: eventually
Component: apps/console Version: 0.9.32
Keywords: transparency, statistics, good-first-ticket Cc:
Parent Tickets: Sensitive: no

Description

The second column of the NetDB overview could benefit from more content. A display of the router count at bandwidth tiers represented in the NetDB could fill the gap.

A count of the total number of routers seen for the session might also be useful.

On a related note, the country count doesn't appear to update after the NetDB is initialized at startup, at least not when seeding manually.

Subtickets

Change History (6)

comment:1 Changed 21 months ago by zzz

Status: newinfoneeded_new

What's the benefit of a bandwidth tiers chart? Who is the audience? If it's for some troubleshooting, what issue would these data help diagnose?

Same question for the routers-per-session count.

On the third point, the initial geoip resolution runs about 5 minutes after startup. This allows some RIs to load in, and keeps the CPU and disk thrashing that geoip causes out of the way until more important things happen.

comment:2 Changed 21 months ago by Reportage

Status: infoneeded_newnew

Providing more statistics that represent the nature of the NetDB from information that is already available but not expressed is informative and gives users a better understanding of I2P's composition without the complexity overhead. Regarding bandwidth tiers, these are already indicated elsewhere in the console, so providing a count of routers represented at the various tiers would consolidate this information.

As for a routers seen per session count, it's another metric that serves to shed light on how the router and network is functioning. Certainly not essential information, but potentially of interest to users that happen to land on the NetDB overview page.

Both proposed counts are arguably of more relevance than the transport count.

comment:3 Changed 18 months ago by zzz

@str4d awaiting your assessment of this, will we do any of it and if so, what release

comment:4 Changed 18 months ago by str4d

Keywords: transparency statistics good-first-ticket added; netdb console bandwidth tiers removed
Milestone: undecidedeventually
Status: newopen

I am all for abstracting away complexity in the routerconsole, and moving more current content under the advanced flag (some of which is done in the UI patchset). It would be great to have more at-a-glance visualizations of router and network health. I implemented similar graphical abstractions in I2P-Bote, and found it very useful.

That said, we do have higher priorities at the moment, so I doubt we'll get to it soon. But it would make for a nice contribution!

comment:5 Changed 15 months ago by zzz

Resolution: wontfix
Status: openclosed

Not going to happen, due to lack of resources. Additionally, anything new to be hidden behind an advanced flag isn't worth doing at all unless absolutely necessary for network troubleshooting.

comment:6 Changed 15 months ago by zzz

Also: Haven't heard any other requests for information on network "composition" and certainly not split out by tier.

Agreed that the transport count chart is barely relevant, candidate for removal or moving behind advanced flag.

Note: See TracTickets for help on using tickets.