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

[Improvement]: SwiftData Performance #168

Open
2 tasks
azooz2003-bit opened this issue Jan 10, 2025 · 0 comments
Open
2 tasks

[Improvement]: SwiftData Performance #168

azooz2003-bit opened this issue Jan 10, 2025 · 0 comments
Labels
enhancement improving existing capabilities

Comments

@azooz2003-bit
Copy link
Contributor

Description

I thought of this RE background thread operations for SwiftData:

  1. The whole time we were passing models created on a background context to the main thread, so it can cause crashes because the model is tied to its own context (background) while we use it on main. And changes on background aren't synchronized with main.
  2. So after doing the BG operations (syncing with API), we return the ids of the models then perform a load on these ids from main so that these models are tied to main.

Relevant Resources

(Feature Owner, Developer) Attach links to resources such as Figma files, technical documentation, etc.

Child Issues

(Developer) Add child issues (technical or high level) that will help you modularize your implementation this feature.

  • Task 1 ...
  • Task 2 ...

When beginning work on a task, click on the ... button to the right of the task and click on Convert to Issue to create a child issue linked to this parent issue.

Implementation Plan (optional)

(Developer) Write an implementation plan here, or attach a link to a document containing it.

@azooz2003-bit azooz2003-bit added the enhancement improving existing capabilities label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement improving existing capabilities
Projects
None yet
Development

No branches or pull requests

1 participant