-
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
Speedup sync chain creation time #2742
Comments
we also need to change fetch time when self delete/reset |
@AlexeyBarabash I see on Linux it takes 8secs as mentioned in #2782 (comment). Is this ok? The expected result says <5secs |
@srirambv |
Thanks for the confirmation @AlexeyBarabash . So anything below 10secs is a reasonable acceptable time I guess Verification passed on
Verification passed on
Verification PASSED on
|
Description
Current update interval for fetch records is 60 sec.
When sync chain is creating, device gets aware about it finished when it does fetch and sees other devices in chain. 60 seconds interval affects this phase so Device2 can appear in the list of devices of Device1 in 60 sec, which may seem too long.
Steps to Reproduce
Actual result:
Device1 gets created a sync chain much later (>15 sec) than Device2
Expected result:
Device1 gets created a sync chain not so late (<5 sec) after Device2
Reproduces how often:
Easily
Brave version (brave://version info)
Reproducible on current release:
The text was updated successfully, but these errors were encountered: