Reduce history notifications traffic for bookmark views
Categories
(Toolkit :: Places, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox85 | --- | fixed |
People
(Reporter: mak, Assigned: mak)
References
Details
Attachments
(7 files)
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details |
With some refactoring, we should be able to:
- remove OnPageChanged
- remove onItemVisited
- stop observing history from the bookmarks service
- Allow bookmark views that don't use nor show history details to not listen for new visits and not notify history details changes to the view
This should allow us to remove one history listener, and reduce the weight of history on bookmark views.
Assignee | ||
Comment 1•4 years ago
|
||
Use the new notifications system to notify about favicon changes, that is the only
part left of onPageChanged.
Assignee | ||
Comment 2•4 years ago
|
||
Depends on D97274
Assignee | ||
Comment 3•4 years ago
|
||
Depends on D97275
Assignee | ||
Comment 4•4 years ago
|
||
Rather than fetching bookmarks from the disk for each page-visited notification,
we just let the result to recursively find and update children in the memory
structure.
Depends on D97276
Assignee | ||
Comment 5•4 years ago
|
||
RunInBatchMode has been removed some time ago, the only thing still sending
these notifications is maintenance to force a UI update, and it can send both.
Depends on D97277
Assignee | ||
Comment 6•4 years ago
|
||
The result can directly listen for page-visited and recursively update children.
With onItemVisited gone, all the reasons for the bookmarks service to listen for
history notifications are gone, thus it can stop observing history.
Depends on D97278
Assignee | ||
Comment 7•4 years ago
|
||
In most cases bookmarks views don't need to be notified of history changes.
The only cases where they need that, is when history columns are visible in a
tree view, or the result is sorted by visits or frecency.
Thus, the menu and toolbar views can often save some work by not listening.
Depends on D97279
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
Backed out for bustages on nsNavHistory.cpp.
Backout link: https://hg.mozilla.org/integration/autoland/rev/841d56a3851bffc64235c064cd4593d1d2bc65f3
Failure log: https://treeherder.mozilla.org/logviewer?job_id=322638939&repo=autoland&lineNumber=87711
Comment 12•4 years ago
|
||
Update to Comment 11:
The patches backed out on https://hg.mozilla.org/integration/autoland/rev/841d56a3851bffc64235c064cd4593d1d2bc65f3
have also caused node newtab failures:
https://treeherder.mozilla.org/jobs?repo=autoland&fromchange=b6178c37f53e6c895dfd76a6ed668b3c2509e3a5&searchStr=linux%2C18.04%2Cx64%2Copt%2Cnode%2Ctests%2Csource-test-node-newtab-unit-tests%2Cnewtab&tochange=841d56a3851bffc64235c064cd4593d1d2bc65f3&selectedTaskRun=Qd1jDdZhQTOQkNNSKFBVdg.0
Assignee | ||
Comment 13•4 years ago
|
||
Thank you, I'm already verifying fixes on Try.
Comment 14•4 years ago
|
||
Comment 15•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/49f8c976469e
https://hg.mozilla.org/mozilla-central/rev/d739ef17da5f
https://hg.mozilla.org/mozilla-central/rev/8684e7486a10
https://hg.mozilla.org/mozilla-central/rev/f7c9fb064c37
https://hg.mozilla.org/mozilla-central/rev/51d608074a74
https://hg.mozilla.org/mozilla-central/rev/bcaf47876119
https://hg.mozilla.org/mozilla-central/rev/9785de91c4fc
Description
•