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.
I found that there was a significant amount of churn during sync. for example, here is some data representing what happened during a routine sync:
notice that 82,973 local entities are deleted and 170k added. this seemed fishy to me, so I investigated.
It turns out that assets are compared to see if they are roughly equal. Part of that is to check if the modified date is within close range. It was using 10ms as wiggle room for the range. But I saw elsewhere 1000ms is used. I bumped the 10 to 1000 in the
equal
method of the asset class and it fixed the comparison problem i was having. These are the results afterwards: