New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 672370 link

Starred by 6 users

Issue metadata

Status: Archived
Owner:
Closed: Sep 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 489470
issue 394296
issue 627922
issue 676659
issue 687005
issue 706458



Sign in to add a comment

Explore IPC rate-limiting / batching mechanism ☂

Project Member Reported by kinuko@chromium.org, Dec 8 2016

Issue description

Explore IPC rate-limiting / batching mechanism

There're number of issues that can be possibly addressed better (rather than keep adding per-module changes) if we have some rate-limiting and/or batching mechanism at IPC layer.

This is a meta-bug to track the issues related to IPC rate-limiting / batching.

 
Not blocking, but possibly related issues (mostly about making loading for bunch of resources faster / more scalable):
 issue 600839 : Move throttling done by ResourceScheduler down into the network stack (have some issues that could be improved by IPC batching)
issue 440037: Creating resource loader stack and starting a URLRequest (ResourceDispatcherHostImpl::BeginRequestInternal) on the IO Thread are both slow
 issue 402136 : Resource request message swamped browser IO thread in telemetry smoothness test (fixed by resource dispatch throttler, but it doesn't work if we migrate to mojo)

Comment 2 by kinuko@chromium.org, Dec 15 2016

Components: Internals>Core Blink>Loader Internals>Mojo

Comment 3 by creis@chromium.org, Jan 6 2017

Blocking: 676659
Blocking: 687005
Blocking: 706458
Issue 556746 has been merged into this issue.
Status: Archived (was: Assigned)
As far as I know we currently are not actively pursuing this route, let me archive this issue.

Sign in to add a comment