microsoft / microsoft/ethr

Long-Running Test to Gather Statistics Throughout a Whole Day

Open
#140 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.9k
Forks
406
PR merge metrics
No merged PRs in 30d

Description

This would be an interesting feature to have available:

Basically, I've ran iperf and also ethr between a pair of servers (one in the cloud and one in our local environment) on a number of occasions because I'd like to get a sense of the overall bandwidth available for the private connection between the two points.

In my earlier iperf tests (the first was a few months back and a more recent one a few weeks back) the connection speed was maybe around 100 Mbps (over what should be gigabit connections on both ends, although the encryption for the private connection is going to reduce that thoroughput overall).

In my test a few moments ago with Ethr, the speeds were more like 350 Mbps and so I'm wondering a few things now (were the iperf results incorrect, is ethr incorrect, or is there a potential speedup explained by an update in the VPN client, or is it timing related, since I'm running this test earlier in the morning?).

It would be nice to leave Ethr running for day (with both the client and server being available, but maybe only running the test once every X minutes) and then have those results compiled together at the end in some way. (Maybe as #74 suggests, or having some additional options such as the full results saved to CSV for further analysis later, or summarized by hour).

Not sure how difficult this would be to implement but it might be a useful bit of functionality for others as well that may have a similar need (I'm open to recommendations for other open-source tools as well that might be able to provide that info as well if Ethr is not a good fit).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are identified in the issue. Start by reviewing Ethr's client and server test-running entry points and the related discussion in #74; done should define periodic measurements over a day and produce compiled results, such as CSV output or hourly summaries.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.