-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recalculate synced bookmark frecencies #847
Milestone
Comments
linabutler
added a commit
that referenced
this issue
Apr 23, 2019
This commit recalculates stale frecencies for synced bookmark URLs, chunking them to allow transactions on the main connection to interrupt frecency calculation. This commit also changes `score_recent_visits` to use the correct timestamp unit: `now()` and `v.visit_date` are in milliseconds, not microseconds as on Desktop. Closes #847.
4 tasks
linabutler
added a commit
that referenced
this issue
Apr 23, 2019
This commit recalculates stale frecencies for synced bookmark URLs, chunking them to allow transactions on the main connection to interrupt frecency calculation. This commit also changes `score_recent_visits` to use the correct timestamp unit: `now()` and `v.visit_date` are in milliseconds, not microseconds as on Desktop. Closes #847.
linabutler
added a commit
that referenced
this issue
Apr 23, 2019
This commit recalculates stale frecencies for synced bookmark URLs, chunking them to allow transactions on the main connection to interrupt frecency calculation. This commit also changes `score_recent_visits` to use the correct timestamp unit: `now()` and `v.visit_date` are in milliseconds, not microseconds as on Desktop. Closes #847.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#723 added a
moz_places_stale_frecencies
table to hold Place IDs with stale frecencies, but doesn't recalculate them yet. It's expensive to recalculate everything using the current frecency algorithm, but there are a few things we could do:The text was updated successfully, but these errors were encountered: