Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Full domain chain snap sync. #3115
Full domain chain snap sync. #3115
Changes from 1 commit
64e54ef
40758d0
b7801f6
ce5f5f4
b2b85f8
ea16060
b9832af
3969d74
4a1404c
f9f87a6
0568ab9
a274f32
bdb738a
859c2cd
bf89a41
eb78e45
b8571cf
c5d4b0f
9956983
44499af
60d45e9
8a035c0
bf34b67
ad6a1f1
6962b8f
74c4f7f
1f78a74
0bed801
7179802
b6e9f84
2267205
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: this is an unusually strong ordering, which might have a performance impact. Usually it is enough to use
Acquire
for loads andRelease
for stores.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll set it to the proposed values. However, I don't think performance suffers here because of the access pattern (write once in total, query once per second). Please, correct me if I'm wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides the domain worker,
SubspaceSyncOracle
is also used in other places of the consensus chain like the archiver, PoT worker and RPC, etc, and if the domain sync is not finished it will change the return value ofis_major_syncing
and some behaviors of these workers, better to have more eyes on this to see if it is okay.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
SeqCst
ordering has an impact on read and write performance, because it imposes a total order across all threads:https://doc.rust-lang.org/std/sync/atomic/enum.Ordering.html#variant.SeqCst
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to my last comment,
Release
should be enough here:https://doc.rust-lang.org/std/sync/atomic/enum.Ordering.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just un-resolving this because Ning wanted more people to review the code.