Skip to content
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

[OPTIMISATION] Server sync dynamic data #2812

Open
chrismclarke opened this issue Feb 24, 2025 · 0 comments
Open

[OPTIMISATION] Server sync dynamic data #2812

chrismclarke opened this issue Feb 24, 2025 · 0 comments

Comments

@chrismclarke
Copy link
Member

chrismclarke commented Feb 24, 2025

Details
When dynamic data is stored, a full row of data is stored locally which can contain a lot of information. This full row is then synced to the server as part of user backup/sync operations, resulting in large payloads (see related #2809)

Recommendations

See sub-issues

Further considerations
Profile restore actions will need to be handled carefully if partial states stored, as the data on the server could represent either minimal write layer as updated onto existing data, or a full row that was created by dynamic data service insert

Additional Information
See example of large sync snapshot below:

example-synced-data.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant