Closed
Bug 623969
Opened 14 years ago
Closed 1 years ago
updatePlaces should only update frecency once per URI
Categories
(Toolkit :: Places, defect, P3)
Toolkit
Places
Tracking
()
RESOLVED
FIXED
116 Branch
People
(Reporter: sdwilsh, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [snt-scrubbed][places-performance])
Right now History::UpdatePlaces will update frecency after every visit. If we have duplicate URIs (likely), this is a lot of extra disk I/O that we don't need to do.
Best bet is probably to a hashtable of ids->VisitData (or spec maybe and change the method) and enumerate them.
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Comment 1•2 years ago
|
||
This requires to investigate a best approach to the problem.
Whiteboard: [snt-scrubbed][places-performance]
|
||
Updated•2 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SNT-550
|
|
||
Comment 2•1 years ago
|
||
This should have been addressed by Bug 1826946. Calculation for any batch insert is now delayed.
Status: NEW → RESOLVED
Closed: 1 years ago
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•