From 0d0fbd6586683278f4c1a92a77d7d6de7b80c285 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 29 Jun 2014 18:25:03 -0700 Subject: [PATCH] =?UTF-8?q?Updated=20=C2=B5Block=20vs.=20ABP:=20efficiency?= =?UTF-8?q?=20compared=20(markdown)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- µBlock-vs.-ABP:-efficiency-compared.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/µBlock-vs.-ABP:-efficiency-compared.md b/µBlock-vs.-ABP:-efficiency-compared.md index fb0c332..c6b522f 100644 --- a/µBlock-vs.-ABP:-efficiency-compared.md +++ b/µBlock-vs.-ABP:-efficiency-compared.md @@ -14,7 +14,7 @@ Both extensions had _EasyList_, _EasyPrivacy_, _Peter Lowe's Ad Server_ list, an ### Added overhead to each net request -ABP and µBlock need to process the URL of each net request against all the filters, and eventually tell the waiting browser whether the request should be cancelled or not. Since the browser is waiting for an answer, this is a time critical part and determining whether the request should be allowed or not must be done as fast as possible. +ABP and µBlock need to evaluate the URL of each net request against their dictionary of filters, and eventually tell the waiting browser whether the request should be cancelled or not. Since the browser is waiting for an answer, this is a time critical part and determining whether the request should be allowed or not must be done as fast as possible. Below are the average time it takes for each extension to handle a net request in their respective `chrome.webRequest.onBeforeRequest` handler, using the same [benchmark](https://github.com/gorhill/uBlock/wiki/Reference-benchmark).