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

Realm-swift is utilising 100-150% CPU when in background #8497

Closed
sportyravi opened this issue Mar 1, 2024 · 3 comments
Closed

Realm-swift is utilising 100-150% CPU when in background #8497

sportyravi opened this issue Mar 1, 2024 · 3 comments
Assignees
Labels
More-information-needed More information is needed to progress. The issue will close automatically in 2 weeks. O-Community

Comments

@sportyravi
Copy link

sportyravi commented Mar 1, 2024

Realm-swift is utilising 100-150% CPU when in background. Our app is having Realm 10.44.0 packaged into the code and we have observed a drastic decrease in performance when app was put into background. I will not be in a position to share screenshots of the code but we observed this behaviour all the time. Request to optimise this performance issue in future releases. App performs CRUD operations when in background.

XCode 15.2
Deployment Target : iPhone
Tested in: iPhone 12 Pro Max, iPhone 13 Pro Max, iPhone 14

Copy link

sync-by-unito bot commented Mar 1, 2024

➤ PM Bot commented:

Jira ticket: RCOCOA-2297

@nirinchev
Copy link
Member

Are you using Sync or is this happening with just the local database. There's nothing obvious that would explain a drop in performance other than just the kernel allocating fewer resources to your app.

If you're able to consistently reproduce the issue, it would help to extract a minimal repro case in a new project and share that with us so that we can profile and address the issues.

@nirinchev nirinchev self-assigned this Mar 1, 2024
@sync-by-unito sync-by-unito bot added the More-information-needed More information is needed to progress. The issue will close automatically in 2 weeks. label Mar 1, 2024
Copy link

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
More-information-needed More information is needed to progress. The issue will close automatically in 2 weeks. O-Community
Projects
None yet
Development

No branches or pull requests

2 participants