Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[webapp] WIP Latency Path Survey #109

Closed
wants to merge 15 commits into from
Closed

Conversation

mwfarb
Copy link
Contributor

@mwfarb mwfarb commented Oct 3, 2019

This change is Reviewable

mwfarb added 5 commits June 20, 2019 12:47
moving path text color fix here

adding test link text

adding latency placeholders in path lists

updated path header, fixed path latency text

adding traceroute last call

convert incoming paths to hash map

tr appears in wrong order, but path latency updates now

use best results

find min/max and report min'

adding stats object to trace needed stats

adding stats to path graph

restore traceroute
@mwfarb
Copy link
Contributor Author

mwfarb commented Oct 3, 2019

There are sill some bugs, but one question I have is the best way to show performance on the topology graph. I can report responses as: Last, Average, Min, or Max.

  • Should we show the performance on the links only, or also show the inter AS performance on the graph?
  • Also in the graph view should we report the latency as the average difference between hops? Or is that too messy when farther nodes report back faster than near ones?
    Screenshot from 2019-10-03 08-45-04

@mwfarb
Copy link
Contributor Author

mwfarb commented Jan 13, 2020

Another PR is more advanced than this one, so closing. See #124.

@mwfarb mwfarb closed this Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant