New issue
Advanced search Search tips

Issue 640074 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Experiment with shorter duration when QUIC packet reader processing packets

Project Member Reported by zhongyi@chromium.org, Aug 23 2016

Issue description

Based on net-internals, it looks like headers coming into Chrome aren't being processed when they're received, and instead are parsed later after 20ms or 32 packets are processed.

It seem to be a potential source for jank we wouldn't want in the network thread. Add field trial experiments to test whether changing the yield time to shorter duration is good for performance.
 
Status: Fixed (was: Started)
By default, we have changed packet reader to yield after 2ms. Manually attach the change log here. 

Default packet reader yield time to 2ms as stable experimental results
shows performance improvement.

Bug: 
Change-Id: I7f40d51e15b19dd5ae6d1b56b9a0167aa7f80b11
Reviewed-on: https://chromium-review.googlesource.com/582327
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#489413}

Sign in to add a comment