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

feat(bwmon): monitor bandwidth usage #531

Draft
wants to merge 13 commits into
base: master
Choose a base branch
from
Draft

feat(bwmon): monitor bandwidth usage #531

wants to merge 13 commits into from

Conversation

bassosimone
Copy link
Contributor

Checklist

  • I have read the contribution guidelines
  • reference issue for this pull request: REFERENCE_ISSUE_URL
  • related ooni/spec pull request: RELATED_OONI_SPEC_PULL_REQUEST_URL

Location of the issue tracker: https://github.com/ooni/probe

Description

This is experimental code that was part of the branch
#506 and that
I am not sure whether it could really be useful when
running in prod, but may be useful for running some
benchmarks of websteps vs webconnectivity.

This is experimental code that was part of the branch
#506 and that
I am not sure whether it could really be useful when
running in prod, but may be useful for running some
benchmarks of websteps vs webconnectivity.
This is the most immediate fix to the issue described by
ooni/probe#1792.

So, the logic was actually miss the increment, which
would have been noticed with proper unit testing.

Anyway, I am not sure why the loop ensues in the first
time. By looking at the headers, it seems we're passing
the headers correctly.

So, even though this fix interrupts the loop, it still
remains the question of whether the loop is legit or
whether we're missing extra logic to properly redirect.
After calibration I can confirm we can provoke losses on both
paths and we can increase delay on both paths.

Likewise, I can apply a TBF w/o netem.
After calibration I can confirm we can provoke losses on both
paths and we can increase delay on both paths.

Likewise, I can apply a TBF w/o netem.
This diff should help us to more easily do A/B testing with parroting.

Unclear whether we want to have this merged into master.
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