New issue
Advanced search Search tips

Issue 757046 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Add a signal in NQE to estimate the last mile congestion.

Project Member Reported by devdeepray@chromium.org, Aug 18 2017

Issue description

Estimate the congestion using the increase in RTT as a signal. The recent RTT observations and the historical RTT observations can be compared to get an estimate of the increase in RTT.

UMA needs to be added to measure the correllation between the increase in RTT and the number of requests in-flight to determine if this can be used as a signal for request throttling.
 

Comment 1 by bengr@chromium.org, Aug 18 2017

Status: Available (was: Untriaged)

Comment 2 by bengr@chromium.org, Aug 18 2017

Owner: ----
Project Member

Comment 3 by bugdroid1@chromium.org, Aug 18 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/275b75a1ca9e551a790757c6ef27ba2faf9409ed

commit 275b75a1ca9e551a790757c6ef27ba2faf9409ed
Author: Devdeep Ray <devdeepray@chromium.org>
Date: Fri Aug 18 23:08:10 2017

Compute the increase in RTT by comparing recent and historical data.

Each NQE RTT observation is tagged with a unique identifier of the
remote subnet for better detection of an increase in RTT due to
congestion. The algorithm takes the minimum RTT from the historical
data and the median RTT from the recent data and computes the increase
in RTT for each subnet. This is combined using a weighted percentile,
where the weight of a subnet is determined by the number of samples 
observed for that subnet.

Bug:  757046 
Change-Id: Id474182c7465afe78793ef325f434d404b0316fd
Reviewed-on: https://chromium-review.googlesource.com/611564
Commit-Queue: Devdeep Ray <devdeepray@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#495730}
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/network_quality_estimator.cc
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/network_quality_estimator.h
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/network_quality_estimator_params.cc
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/network_quality_estimator_params.h
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/network_quality_estimator_unittest.cc
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/network_quality_estimator_util.h
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/network_quality_observation.cc
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/network_quality_observation.h
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/observation_buffer.cc
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/observation_buffer.h
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/observation_buffer_unittest.cc
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/socket_watcher.cc
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/socket_watcher.h
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/socket_watcher_factory.h
[modify] https://crrev.com/275b75a1ca9e551a790757c6ef27ba2faf9409ed/net/nqe/socket_watcher_unittest.cc

Comment 4 by bengr@chromium.org, Aug 29 2017

Status: Started (was: Available)

Comment 5 by bengr@chromium.org, Dec 1 2017

Cc: -tbansal@chromium.org
Status: tbansalchromium.org (was: Started)
What's the status? Is this still needed?
Refreshed during triage.
Refreshed during triage.

Comment 8 by bengr@chromium.org, May 2 2018

Cc: tbansal@chromium.org
Status: Available (was: tbansalchromium.org)
This should help in improving resource scheduling.

Comment 10 by tbansal@chromium.org, Jan 18 (5 days ago)

Status: WontFix (was: Available)

Sign in to add a comment