IconCacher is triggered too often by MostVisitedSites |
||||
Issue descriptionIconCacher is usually triggered several times in a quick succession for the same set of tiles. This causes concurrent network request. This happens for both MostLikely tiles (usually triggered 3 times or even more) and for PopularSites (usually triggered twice).
,
May 11 2017
I did not make myself clear: I care only about concurrent *redundant* requests (for the same tile/URL). I do not prefer sequential. I prefer asking only once for each tile. You are right that we do not issue multiple network requests. Still it feels silly to ask the FaviconService 3 times in one second for the very same favicon.
,
May 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fc015b3cb9d91a89707e479635fad2cd3695cd1d commit fc015b3cb9d91a89707e479635fad2cd3695cd1d Author: jkrcal <jkrcal@chromium.org> Date: Thu May 18 17:43:21 2017 [NTP Tiles] Avoid duplicate requests from IconCacherImpl This CL adds recording of requests in-flight so that we do not issue the same network request twice. The cacher is often triggered both for PS and for ML several times in a quick succession. This is a kind of a hack to make experimentation with fetching favicons for MostLikely tiles in M60 safer (not issuing too many network requests). This should be removed once the underlying issue in most_visited_sites is addressed. BUG=720536 Review-Url: https://codereview.chromium.org/2873403002 Cr-Commit-Position: refs/heads/master@{#472861} [modify] https://crrev.com/fc015b3cb9d91a89707e479635fad2cd3695cd1d/components/ntp_tiles/icon_cacher_impl.cc [modify] https://crrev.com/fc015b3cb9d91a89707e479635fad2cd3695cd1d/components/ntp_tiles/icon_cacher_impl.h [modify] https://crrev.com/fc015b3cb9d91a89707e479635fad2cd3695cd1d/components/ntp_tiles/icon_cacher_impl_unittest.cc
,
Sep 27 2017
,
Sep 28
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 1
|
||||
►
Sign in to add a comment |
||||
Comment 1 by fhorschig@chromium.org
, May 11 2017