From 05cc4e799b897a440333d3dbe6d18b904a49759f Mon Sep 17 00:00:00 2001 From: "mpcomplete@chromium.org" Date: Tue, 8 Mar 2011 21:29:48 +0000 Subject: Implement blocking for webRequest.onBeforeRequest extension event. I did some measurements with a Release build of chrome, both manually and via the page cycler tests. It seems that a simple empty blocking event listener can add anywhere from a 1 to 30ms delay to request times, largely depending on how many requests are in the queue (when many requests come at once, the last ones to be processed by the extension are delayed the longest). From page cycler data (on my local machine), the average increase in page load time seems to be around 6ms. This is independent of total page load time (which makes sense). BUG=60101 TEST=covered by apitests Review URL: http://codereview.chromium.org/6574049 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77339 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/io_thread.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'chrome/browser/io_thread.cc') diff --git a/chrome/browser/io_thread.cc b/chrome/browser/io_thread.cc index 9a0e035..4324b60 100644 --- a/chrome/browser/io_thread.cc +++ b/chrome/browser/io_thread.cc @@ -336,7 +336,7 @@ void IOThread::Init() { globals_->extension_event_router_forwarder = extension_event_router_forwarder_; globals_->system_network_delegate.reset(new ChromeNetworkDelegate( - extension_event_router_forwarder_, Profile::kInvalidProfileId)); + extension_event_router_forwarder_, Profile::kInvalidProfileId)); globals_->host_resolver.reset( CreateGlobalHostResolver(net_log_)); globals_->cert_verifier.reset(new net::CertVerifier); -- cgit v1.1