|
|
Chromium Code Reviews
DescriptionRecord the time duration for establishing proxy connection
Different UMA histograms are used for secure and insecure proxies.
Similarly, different histograms are used when the proxy connection was
successful vs. when the connection attempt timed out.
BUG=704339
Review-Url: https://codereview.chromium.org/2768173002
Cr-Commit-Position: refs/heads/master@{#460216}
Committed: https://chromium.googlesource.com/chromium/src/+/4cbf5c1bc96f24e9e660e538cdce3d00562626f4
Patch Set 1 #
Total comments: 4
Patch Set 2 : Address error histogram #
Messages
Total messages: 33 (21 generated)
Description was changed from ========== Record UMA BUG= ========== to ========== Record the time duration for establishing proxy connection Different UMA histogram is used for secure and insecure proxies. Similarly, different histogram is used when the proxy connection was successful vs. when the connection attempt timed out. BUG= ==========
tbansal@chromium.org changed reviewers: + ryansturm@chromium.org
ryansturm: ptal. Thanks.
Description was changed from ========== Record the time duration for establishing proxy connection Different UMA histogram is used for secure and insecure proxies. Similarly, different histogram is used when the proxy connection was successful vs. when the connection attempt timed out. BUG= ========== to ========== Record the time duration for establishing proxy connection Different UMA histogram is used for secure and insecure proxies. Similarly, different histogram is used when the proxy connection was successful vs. when the connection attempt timed out. BUG=704339 ==========
tbansal@chromium.org changed reviewers: + mmenke@chromium.org - ryansturm@chromium.org
mmenke: ptal. Thanks.
Description was changed from ========== Record the time duration for establishing proxy connection Different UMA histogram is used for secure and insecure proxies. Similarly, different histogram is used when the proxy connection was successful vs. when the connection attempt timed out. BUG=704339 ========== to ========== Record the time duration for establishing proxy connection Different UMA histograms are used for secure and insecure proxies. Similarly, different histograms are used when the proxy connection was successful vs. when the connection attempt timed out. BUG=704339 ==========
On 2017/03/22 23:24:32, tbansal1 wrote: > mmenke: ptal. Thanks. I'll take a look tomorrow (Main thing I want to do is verify that this covers the right set of proxies).
The CQ bit was checked by tbansal@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: ios-simulator on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
LGTM, modulo comment. Didn't look at the test. https://codereview.chromium.org/2768173002/diff/1/net/http/http_proxy_client_... File net/http/http_proxy_client_socket_wrapper.cc (right): https://codereview.chromium.org/2768173002/diff/1/net/http/http_proxy_client_... net/http/http_proxy_client_socket_wrapper.cc:511: base::TimeTicks::Now() - connect_start_time_); These names should make it clear that they're only for Http proxies.
https://codereview.chromium.org/2768173002/diff/1/net/http/http_proxy_client_... File net/http/http_proxy_client_socket_wrapper.cc (right): https://codereview.chromium.org/2768173002/diff/1/net/http/http_proxy_client_... net/http/http_proxy_client_socket_wrapper.cc:632: next_state_ == STATE_SSL_CONNECT_COMPLETE) { One other question: What about other errors? Looks like we're currently ignoring them. HTTPS auth case looks kinda funky, too (Not sure about HTTP auth, didn't think about it).
The CQ bit was checked by tbansal@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
https://codereview.chromium.org/2768173002/diff/1/net/http/http_proxy_client_... File net/http/http_proxy_client_socket_wrapper.cc (right): https://codereview.chromium.org/2768173002/diff/1/net/http/http_proxy_client_... net/http/http_proxy_client_socket_wrapper.cc:511: base::TimeTicks::Now() - connect_start_time_); On 2017/03/27 16:36:33, mmenke wrote: > These names should make it clear that they're only for Http proxies. Done. https://codereview.chromium.org/2768173002/diff/1/net/http/http_proxy_client_... net/http/http_proxy_client_socket_wrapper.cc:632: next_state_ == STATE_SSL_CONNECT_COMPLETE) { On 2017/03/27 16:39:11, mmenke wrote: > One other question: What about other errors? Looks like we're currently > ignoring them. HTTPS auth case looks kinda funky, too (Not sure about HTTP > auth, didn't think about it). Yes, this histogram records time until only the timeout error. Right now, it is not probably very meaningful since all values are going to be 10 seconds (or 30 seconds). Once I start the dynamic timeout experiment, it will be useful. I have also added histogram for other errors.
mmenke: ptal for PS#2. Thanks.
On 2017/03/27 18:29:44, tbansal1 wrote: > mmenke: ptal for PS#2. Thanks. Still LGTM
tbansal@chromium.org changed reviewers: + rkaplow@chromium.org
rkaplow: ptal at histograms.xml. Thanks.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm
The CQ bit was checked by tbansal@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by tbansal@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 20001, "attempt_start_ts": 1490730991763710,
"parent_rev": "3e2545eea28039a76b9c056c84fddac3cbc9d7d8", "commit_rev":
"4cbf5c1bc96f24e9e660e538cdce3d00562626f4"}
Message was sent while issue was closed.
Description was changed from ========== Record the time duration for establishing proxy connection Different UMA histograms are used for secure and insecure proxies. Similarly, different histograms are used when the proxy connection was successful vs. when the connection attempt timed out. BUG=704339 ========== to ========== Record the time duration for establishing proxy connection Different UMA histograms are used for secure and insecure proxies. Similarly, different histograms are used when the proxy connection was successful vs. when the connection attempt timed out. BUG=704339 Review-Url: https://codereview.chromium.org/2768173002 Cr-Commit-Position: refs/heads/master@{#460216} Committed: https://chromium.googlesource.com/chromium/src/+/4cbf5c1bc96f24e9e660e538cdce... ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001) as https://chromium.googlesource.com/chromium/src/+/4cbf5c1bc96f24e9e660e538cdce... |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
