-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Don't do explicit on demand component update check while startup #12983
Comments
You're aware of this @simonhong but just to give others who read this some context. There are two different kinds of update checks when it comes to components: Automatic and on-demand. Automatic updates are currently broken (#10464) but will likely be fixed soon. As far as I am aware, installation of a component works by registering it with version Brave currently relies on auto-update checks being broken by leaving unwanted Google components in the A key difference between automatic and on-demand updates are that the former requests an update for all currently registered components, while the latter only requests an update for a single component. There already is a delayed automatic update check that happens 60 seconds after Brave is started. See To implement this issue, it might therefore be enough to remove those on-demand update checks that are not necessary, and wait the 60 seconds for the built-in automatic check. |
@mherrmann Many thanks for great explaination!! |
Could we spread the update load for each individual component? |
@simonhong flagging that user-model-installer should be loaded right during startup since if resources are not present users won’t see ads. cc @tmancey |
@ryanbr Not possible now but I think it's worth to try. Currently all components update checks are triggered at once. |
By the way: how to disable auto update |
Maybe we have to do explicit update check during the startup for some components but not all.
With delayed update check(ex, 1 or 5 mins later), we could speed up startup performance a little bit.
The text was updated successfully, but these errors were encountered: