ResourceLoadScheduler: do not take the priority into account
The current logic has an exception not to throttle the kHigh priority requests even if the request is marked as kThrottleable. However, this exception makes the per-frame maximum limit useless, and make requests result in failure for hitting the network service resource limit. This patch enforces the normal limit even for the kHigh requests for both throttling policies. But still kHigh requests can escape from the tight throttling. Bug: 1046882 Change-Id: I4e167fdb667f9adc90604fa1d65fc4cd6e650c8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028886Reviewed-by:Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#737677}
Showing
Please register or sign in to comment