Status: Untriaged Owner: ---- Labels: Type-Other Pri-3 OS-All Area-BrowserBackend
New issue 6796 by pkast...@chromium.org: Ensure Gears interceptors do not cause perf hits http://code.google.com/p/chromium/issues/detail?id=6796 A 1% perf hit we took on the DHTML page cycler was never fully explained but led to the following worry: "Making an HTTP request calls us to load in Gears and hook up the interceptors. They won't actually do much for file: requests, but they'll at least cause us to make a virtual function call and a hash table lookup on every request. I can try commenting this stuff out and seeing what effect it has. We could also try commenting this out, or doing something more drastic with Gears, and seeing what effect the HTML page cyclers show, to make sure our current Gears code is not hurting real perf too much." This bug is about investigating to ensure Gears interceptors have zero, or as little as possible, perf impact. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
