New issue
Advanced search Search tips

Issue 692215 link

Starred by 2 users
Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: 2019-01-08
OS: All
Pri: 3
Type: Feature



Sign in to add a comment

Lengthen history expiry period

Project Member Reported by pkasting@chromium.org, Feb 14 2017 
History expiry can result in bad omnibox quality.  If we can lengthen it, we should.

Moving to flat containers for the omnibox might get enough perf win to let us expand this.

It might be hard to measure the statistical benefits of this.  I would expect the biggest benefit to be in users not getting occasional surprising behavior where something they expected to appear didn't.  This wouldn't happen regularly enough to be very measurable.  Personally, I would be OK with a change here that was stat-neutral.

Comment 1 by pkasting@chromium.org, Feb 15 2017 

In the code, this is supposedly 90 days currently.  (I'm not 100% sure that's actually what happens at runtime due to bugs.)  I'd love to see us lengthen this to a year and get a sense of the perf impact.

Note that this also interacts with the "low quality visit thresholds" -- loosening those and lengthening this both have the effect of making us more willing to score matches which have not been visited much within the past ninety days.

Comment 2 by pkasting@chromium.org, Feb 15 2017 

(See bug 692386 regarding the last paragraph of comment 1.)

Comment 3 by mpear...@chromium.org, Jun 26 2017

Labels: -Pri-2 Pri-3
NextAction: 2018-01-09
We're actually experimenting with decreasing the size of the history database, at least HQP's one.  This so far is quality-neutral on omnibox measurements on dev.  I think people (at least on Android) would appreciate the memory more than a different quality-neutral change in the other direction.

Punting to re-assess next year when the shrinking omnibox history database experiments are finished.

Comment 4 by mpear...@chromium.org, Jul 19 2017

Labels: Hotlist-OmniboxRanking

Comment 5 by mpear...@chromium.org, Dec 14 2017 

"expiration" and "expires" are a useful keywords to have on this bug, both previously lacking.

Comment 6 by monor...@bugs.chromium.org, Jan 9 2018 

The NextAction date has arrived: 2018-01-09
Project Member

Comment 7 by sheriffbot@chromium.org, Dec 17

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Comment 8 by mpear...@chromium.org, Dec 17

NextAction: 2019-01-08
Status: Available (was: Untriaged)
Still low-priority, as we don't commonly hear of cases where this will help.

Comment 9 by monor...@bugs.chromium.org, Jan 8 

The NextAction date has arrived: 2019-01-08
►

Sign in to add a comment