234
edits
User:Sspitzer/GlobalFrecency: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
''' | '''where to find the builds''' | ||
https://build.mozilla.org/tryserver-builds/2008-01-10_16:09-sspitzer@mozilla.com-1200010016/ | https://build.mozilla.org/tryserver-builds/2008-01-10_16:09-sspitzer@mozilla.com-1200010016/ | ||
Big picture view of the changes | '''Big picture view of the changes''' | ||
1) unvisited bookmarks will appear in url bar autocomplete (ac) results. this means if you clear private data, if you have bookmarks, url bar ac still has something to return upon typing. | 1) unvisited bookmarks will appear in url bar autocomplete (ac) results. this means if you clear private data, if you have bookmarks, url bar ac still has something to return upon typing. | ||
| Line 11: | Line 11: | ||
if a highly ranked (by frececny) site was visited more than 4 days ago, unlike before, it will appear in the first set of results. so say you visit http://wiki.mozilla.org/WeeklyUpdates once a week for the past year, but it's been 7 days since your last visit. before, because it was more than 4 days old, it would not be in the first chunk of results. | if a highly ranked (by frececny) site was visited more than 4 days ago, unlike before, it will appear in the first set of results. so say you visit http://wiki.mozilla.org/WeeklyUpdates once a week for the past year, but it's been 7 days since your last visit. before, because it was more than 4 days old, it would not be in the first chunk of results. | ||
Additonal details | '''Additonal details''' | ||
1) Unlike before, unvisited bookmarks should appear in ac results | 1) Unlike before, unvisited bookmarks should appear in ac results | ||
| Line 25: | Line 25: | ||
7) When inserting a bookmark, we attempt to calculate a frecency for it. This will impact the performance of bookmark import and also fx 2 - > fx 3 migration. (spin off bug coming about how to deal with it.) | 7) When inserting a bookmark, we attempt to calculate a frecency for it. This will impact the performance of bookmark import and also fx 2 - > fx 3 migration. (spin off bug coming about how to deal with it.) | ||
8) for how we calculate a freceny for a site, see http://wiki.mozilla.org/User:Mconnor/PlacesFrecency (and option 3). I use the 10 most recent visits | 8) for how we calculate a freceny for a site, see http://wiki.mozilla.org/User:Mconnor/PlacesFrecency (and option 3). I use the 10 most recent visits, and this is pref controlled, as all are the buckets, weights and bonus values. | ||
9) | 9) if we don't have any visits for a site, I make an attempt to estimate the frecency. more on this in a spin off bug (including when we should estimate and when we should not.) | ||
10) | 10) After only 5 seconds of idle, I'll attempt to recalculate the top 100 invalid frecencies (ordered by visit count) and the top 100 "old" frecencies (order by frecency descending but the last visit date is older than 4 days). 4 days is not hard coded, it's really older than the first "bucket". | ||
The 5 second number will increase and the 100 number will decrease before I land. | |||
'''notes to clean up''' | 11) after clearing all private data, all remaining places get the frecency of -1, except for livemark items and "place:" urls (which should get frecency 0). | ||
''' current list of prefs to tune ''' | |||
The names and default values will most likely be changing. I wouldn't recommend tuning these yet. I'll elaborate on what each pref does later on in this document. | |||
+// the (maximum) number of the recent visits to sample | |||
+// when calculating frecency | |||
+pref("browser.frecency.numVisits", 10); | |||
+ | |||
+// buckets (in days) for frecency calculation | |||
+pref("browser.frecency.firstBucketCuttoff", 4); | |||
+pref("browser.frecency.secondBucketCuttoff", 14); | |||
+pref("browser.frecency.thirdBucketCuttoff", 31); | |||
+pref("browser.frecency.fourthBucketCuttoff", 90); | |||
+ | |||
+// weights for buckets for frecency calculations | |||
+pref("browser.frecency.firstBucketWeight", 100); | |||
+pref("browser.frecency.secondBucketWeight", 70); | |||
+pref("browser.frecency.thirdBucketWeight", 50); | |||
+pref("browser.frecency.fourthBucketWeight", 30); | |||
+pref("browser.frecency.defaultBucketWeight", 10); | |||
+ | |||
+// bonus (in percent) for visit transition types for frecency calculations | |||
+pref("browser.frecency.embedVisitBonus", 0); | |||
+pref("browser.frecency.linkVisitBonus", 120); | |||
+pref("browser.frecency.typedVisitBonus", 200); | |||
+pref("browser.frecency.bookmarkVisitBonus", 140); | |||
+pref("browser.frecency.downloadVisitBonus", 0); | |||
+pref("browser.frecency.permRedirectVisitBonus", 0); | |||
+pref("browser.frecency.tempRedirectVisitBonus", 0); | |||
+pref("browser.frecency.defaultVisitBonus", 0); | |||
+ | |||
+// bonus (in percent) for place types for frecency calculations | |||
+pref("browser.frecency.unvisitedBookmarkBonus", 140); | |||
+pref("browser.frecency.unvisitedTypedBonus", 200); | |||
'''Additional notes (need to clean these up, log spin off bugs, etc). These are mostly for dietrich so he knows what I've done and why and the known issues.''' | |||
1) | 1) | ||