This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
bookmarksStorage.getBookmarksWithUrl takes unexpectedly long time (10 - 50ms) #6370
Labels
Comments
mcomella
added this to Needs prioritization
in Performance, front-end roadmap
via automation
Oct 31, 2019
severinrudie
added a commit
to severinrudie/fenix
that referenced
this issue
Oct 31, 2019
This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`.
severinrudie
added a commit
to severinrudie/fenix
that referenced
this issue
Nov 1, 2019
This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`.
severinrudie
added a commit
to severinrudie/fenix
that referenced
this issue
Nov 5, 2019
This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`.
mcomella
moved this from Needs prioritization
to In progress
in Performance, front-end roadmap
Nov 5, 2019
severinrudie
added a commit
to severinrudie/fenix
that referenced
this issue
Nov 6, 2019
This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`.
severinrudie
added a commit
to severinrudie/fenix
that referenced
this issue
Nov 7, 2019
This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`.
severinrudie
added a commit
to severinrudie/fenix
that referenced
this issue
Nov 8, 2019
This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`.
severinrudie
added a commit
to severinrudie/fenix
that referenced
this issue
Nov 11, 2019
This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`.
severinrudie
added a commit
to severinrudie/fenix
that referenced
this issue
Nov 11, 2019
This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`.
severinrudie
pushed a commit
that referenced
this issue
Nov 12, 2019
* For #4281: small ToolbarMenu refactor This makes it easier to see how items are ordered in the menuItems list * For 4281: add QAB buttons to menu * For 4281: removed menu back button per mocks I double checked with UX, and we'll be relying on the hardware back button for its functionality * For 4281: add content descriptions for bookmarking * For 4281: updated BrowserToolbarController for new functionality * For 4281: provided simple dependencies to browser controller More complex changes will be in a following commit, for review readability * For 4281: move toolbar controller dependencies up to BaseBrowserFragment The functionality they control is being moved into the toolbar menu, which is shared by both normal tabs and custom ones * For 4281: removed (now unused) code related to QAB * For 4281: fix test compilation after QAB removal Tests still need to be expanded to include added functionality * For 4281: updated menu to show if url is bookmarked This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. #6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`. * For 4281: update reader mode switch * For 4281: selectively show/hide menu items * For 4281: add reader mode appearance * For 4281: update bookmark button when it is clicked * For 4281: removed unused QAB code * For 4281: removed QAB robot, updated UI tests * For 4281: removed QuickActionSheet metrics Since this behavior now lives in the toolbar, it is tracked via Event.BrowserMenuItemTapped * For 4281: fixed lint errors * For 4281: add new strings for buttons added to menu This is necessary because the location change (from QAB to toolbar menu) could affect the grammar in some languages * For 4281: remove outdated TODOs * For 4281: removed QAB container * For 4281: removed back button reference from UI test This button no longer exists * For 4821: Fixes a visual defect (extra padding on top of toolbar) * For 4281: update copy on reader mode * For 4281: fixed review nits
mozilla-l10n-automation-bot
pushed a commit
to mozilla-l10n-automation-bot/android-l10n
that referenced
this issue
Nov 12, 2019
* For #4281: small ToolbarMenu refactor This makes it easier to see how items are ordered in the menuItems list * For 4281: add QAB buttons to menu * For 4281: removed menu back button per mocks I double checked with UX, and we'll be relying on the hardware back button for its functionality * For 4281: add content descriptions for bookmarking * For 4281: updated BrowserToolbarController for new functionality * For 4281: provided simple dependencies to browser controller More complex changes will be in a following commit, for review readability * For 4281: move toolbar controller dependencies up to BaseBrowserFragment The functionality they control is being moved into the toolbar menu, which is shared by both normal tabs and custom ones * For 4281: removed (now unused) code related to QAB * For 4281: fix test compilation after QAB removal Tests still need to be expanded to include added functionality * For 4281: updated menu to show if url is bookmarked This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile/fenix#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`. * For 4281: update reader mode switch * For 4281: selectively show/hide menu items * For 4281: add reader mode appearance * For 4281: update bookmark button when it is clicked * For 4281: removed unused QAB code * For 4281: removed QAB robot, updated UI tests * For 4281: removed QuickActionSheet metrics Since this behavior now lives in the toolbar, it is tracked via Event.BrowserMenuItemTapped * For 4281: fixed lint errors * For 4281: add new strings for buttons added to menu This is necessary because the location change (from QAB to toolbar menu) could affect the grammar in some languages * For 4281: remove outdated TODOs * For 4281: removed QAB container * For 4281: removed back button reference from UI test This button no longer exists * For 4821: Fixes a visual defect (extra padding on top of toolbar) * For 4281: update copy on reader mode * For 4281: fixed review nits X-Channel-Revision: [master] mozilla-mobile/android-components@ba3f75e X-Channel-Converted-Revision: [master] mozilla-mobile/fenix@6909a76 X-Channel-Revision: [master] mozilla-mobile/firefox-tv@e8ccd59 X-Channel-Revision: [master] MozillaReality/FirefoxReality@ebc151c X-Channel-Revision: [master] mozilla-lockwise/lockwise-android@e070cfc
mozilla-l10n-automation-bot
pushed a commit
to mozilla-l10n-automation-bot/android-l10n
that referenced
this issue
Nov 12, 2019
* For #4281: small ToolbarMenu refactor This makes it easier to see how items are ordered in the menuItems list * For 4281: add QAB buttons to menu * For 4281: removed menu back button per mocks I double checked with UX, and we'll be relying on the hardware back button for its functionality * For 4281: add content descriptions for bookmarking * For 4281: updated BrowserToolbarController for new functionality * For 4281: provided simple dependencies to browser controller More complex changes will be in a following commit, for review readability * For 4281: move toolbar controller dependencies up to BaseBrowserFragment The functionality they control is being moved into the toolbar menu, which is shared by both normal tabs and custom ones * For 4281: removed (now unused) code related to QAB * For 4281: fix test compilation after QAB removal Tests still need to be expanded to include added functionality * For 4281: updated menu to show if url is bookmarked This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile/fenix#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`. * For 4281: update reader mode switch * For 4281: selectively show/hide menu items * For 4281: add reader mode appearance * For 4281: update bookmark button when it is clicked * For 4281: removed unused QAB code * For 4281: removed QAB robot, updated UI tests * For 4281: removed QuickActionSheet metrics Since this behavior now lives in the toolbar, it is tracked via Event.BrowserMenuItemTapped * For 4281: fixed lint errors * For 4281: add new strings for buttons added to menu This is necessary because the location change (from QAB to toolbar menu) could affect the grammar in some languages * For 4281: remove outdated TODOs * For 4281: removed QAB container * For 4281: removed back button reference from UI test This button no longer exists * For 4821: Fixes a visual defect (extra padding on top of toolbar) * For 4281: update copy on reader mode * For 4281: fixed review nits X-Channel-Revision: [master] mozilla-mobile/android-components@ba3f75e X-Channel-Converted-Revision: [master] mozilla-mobile/fenix@6909a76 X-Channel-Revision: [master] mozilla-mobile/firefox-tv@e8ccd59 X-Channel-Revision: [master] MozillaReality/FirefoxReality@ebc151c X-Channel-Revision: [master] mozilla-lockwise/lockwise-android@e070cfc
mozilla-l10n-automation-bot
pushed a commit
to mozilla-l10n-automation-bot/android-l10n
that referenced
this issue
Nov 12, 2019
* For #4281: small ToolbarMenu refactor This makes it easier to see how items are ordered in the menuItems list * For 4281: add QAB buttons to menu * For 4281: removed menu back button per mocks I double checked with UX, and we'll be relying on the hardware back button for its functionality * For 4281: add content descriptions for bookmarking * For 4281: updated BrowserToolbarController for new functionality * For 4281: provided simple dependencies to browser controller More complex changes will be in a following commit, for review readability * For 4281: move toolbar controller dependencies up to BaseBrowserFragment The functionality they control is being moved into the toolbar menu, which is shared by both normal tabs and custom ones * For 4281: removed (now unused) code related to QAB * For 4281: fix test compilation after QAB removal Tests still need to be expanded to include added functionality * For 4281: updated menu to show if url is bookmarked This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile/fenix#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`. * For 4281: update reader mode switch * For 4281: selectively show/hide menu items * For 4281: add reader mode appearance * For 4281: update bookmark button when it is clicked * For 4281: removed unused QAB code * For 4281: removed QAB robot, updated UI tests * For 4281: removed QuickActionSheet metrics Since this behavior now lives in the toolbar, it is tracked via Event.BrowserMenuItemTapped * For 4281: fixed lint errors * For 4281: add new strings for buttons added to menu This is necessary because the location change (from QAB to toolbar menu) could affect the grammar in some languages * For 4281: remove outdated TODOs * For 4281: removed QAB container * For 4281: removed back button reference from UI test This button no longer exists * For 4821: Fixes a visual defect (extra padding on top of toolbar) * For 4281: update copy on reader mode * For 4281: fixed review nits X-Channel-Revision: [master] mozilla-mobile/android-components@ba3f75e X-Channel-Converted-Revision: [master] mozilla-mobile/fenix@6909a76 X-Channel-Revision: [master] mozilla-mobile/firefox-tv@e8ccd59 X-Channel-Revision: [master] MozillaReality/FirefoxReality@ebc151c X-Channel-Revision: [master] mozilla-lockwise/lockwise-android@e070cfc
mozilla-l10n-automation-bot
pushed a commit
to mozilla-l10n-automation-bot/android-l10n
that referenced
this issue
Nov 12, 2019
* For #4281: small ToolbarMenu refactor This makes it easier to see how items are ordered in the menuItems list * For 4281: add QAB buttons to menu * For 4281: removed menu back button per mocks I double checked with UX, and we'll be relying on the hardware back button for its functionality * For 4281: add content descriptions for bookmarking * For 4281: updated BrowserToolbarController for new functionality * For 4281: provided simple dependencies to browser controller More complex changes will be in a following commit, for review readability * For 4281: move toolbar controller dependencies up to BaseBrowserFragment The functionality they control is being moved into the toolbar menu, which is shared by both normal tabs and custom ones * For 4281: removed (now unused) code related to QAB * For 4281: fix test compilation after QAB removal Tests still need to be expanded to include added functionality * For 4281: updated menu to show if url is bookmarked This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile/fenix#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`. * For 4281: update reader mode switch * For 4281: selectively show/hide menu items * For 4281: add reader mode appearance * For 4281: update bookmark button when it is clicked * For 4281: removed unused QAB code * For 4281: removed QAB robot, updated UI tests * For 4281: removed QuickActionSheet metrics Since this behavior now lives in the toolbar, it is tracked via Event.BrowserMenuItemTapped * For 4281: fixed lint errors * For 4281: add new strings for buttons added to menu This is necessary because the location change (from QAB to toolbar menu) could affect the grammar in some languages * For 4281: remove outdated TODOs * For 4281: removed QAB container * For 4281: removed back button reference from UI test This button no longer exists * For 4821: Fixes a visual defect (extra padding on top of toolbar) * For 4281: update copy on reader mode * For 4281: fixed review nits X-Channel-Revision: [master] mozilla-mobile/android-components@ba3f75e X-Channel-Converted-Revision: [master] mozilla-mobile/fenix@6909a76 X-Channel-Revision: [master] mozilla-mobile/firefox-tv@e8ccd59 X-Channel-Revision: [master] MozillaReality/FirefoxReality@ebc151c X-Channel-Revision: [master] mozilla-lockwise/lockwise-android@e070cfc
mozilla-l10n-automation-bot
pushed a commit
to mozilla-l10n-automation-bot/android-l10n
that referenced
this issue
Nov 12, 2019
* For #4281: small ToolbarMenu refactor This makes it easier to see how items are ordered in the menuItems list * For 4281: add QAB buttons to menu * For 4281: removed menu back button per mocks I double checked with UX, and we'll be relying on the hardware back button for its functionality * For 4281: add content descriptions for bookmarking * For 4281: updated BrowserToolbarController for new functionality * For 4281: provided simple dependencies to browser controller More complex changes will be in a following commit, for review readability * For 4281: move toolbar controller dependencies up to BaseBrowserFragment The functionality they control is being moved into the toolbar menu, which is shared by both normal tabs and custom ones * For 4281: removed (now unused) code related to QAB * For 4281: fix test compilation after QAB removal Tests still need to be expanded to include added functionality * For 4281: updated menu to show if url is bookmarked This sloppy workaround is required because TwoStateButton requires that `isInPrimaryState` be a synchronous call, and checking whether or not the current site is bookmarked is quite slow (10-50 MS, in my tests). After days of work and many attempted solutions, this was the least abhorrent among them. mozilla-mobile/android-components#4915 was opened against AC to evaluate potentially supporting async `isInPrimaryState` functions. mozilla-mobile/fenix#6370 was opened against Fenix to investigate the unexpectedly slow call to `BookmarkStorage`. * For 4281: update reader mode switch * For 4281: selectively show/hide menu items * For 4281: add reader mode appearance * For 4281: update bookmark button when it is clicked * For 4281: removed unused QAB code * For 4281: removed QAB robot, updated UI tests * For 4281: removed QuickActionSheet metrics Since this behavior now lives in the toolbar, it is tracked via Event.BrowserMenuItemTapped * For 4281: fixed lint errors * For 4281: add new strings for buttons added to menu This is necessary because the location change (from QAB to toolbar menu) could affect the grammar in some languages * For 4281: remove outdated TODOs * For 4281: removed QAB container * For 4281: removed back button reference from UI test This button no longer exists * For 4821: Fixes a visual defect (extra padding on top of toolbar) * For 4281: update copy on reader mode * For 4281: fixed review nits X-Channel-Revision: [master] mozilla-mobile/android-components@ba3f75e X-Channel-Converted-Revision: [master] mozilla-mobile/fenix@6909a76 X-Channel-Revision: [master] mozilla-mobile/firefox-tv@e8ccd59 X-Channel-Revision: [master] MozillaReality/FirefoxReality@ebc151c X-Channel-Revision: [master] mozilla-lockwise/lockwise-android@e070cfc
@ecsmyth This is called when:
Since this happens off the main thread, I think it's probably unimportant. |
Based on @mcomella's comment, I'm dropping the priority to P2 to align with proposed performance release criteria. |
mcomella
moved this from In progress
to Needs prioritization
in Performance, front-end roadmap
Jan 6, 2020
Fenix uses the P* labels, not us, so replacing the label and sending back to triage. |
mcomella
moved this from Needs prioritization
to Low impact (unprioritized)
in Performance, front-end roadmap
Jan 21, 2020
See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Performance, front-end roadmap
automation
moved this from Low impact (unprioritized)
to Done
Feb 11, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Severin mentioned to me that:
bookmarksStorage.getBookmarksWithUrl(session.url).firstOrNull { it.url == session.url }
(source) takes anywhere from 10-50 MS in a unit test even if there are a small number of bookmarks, like 4: this is an unexpectedly long time.
We should investigate possible causes.
I wonder if the unit test call sthis before the DB is initialized (e.g. initial data creation, or even just loading the DB from disk) so calling this sets up the DB and is what makes this take a long time, but we wouldn't see this in practice.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: