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

Reduce memory footprint on registers and profiles #3608

Open
ellykits opened this issue Nov 14, 2024 · 0 comments · May be fixed by #3634
Open

Reduce memory footprint on registers and profiles #3608

ellykits opened this issue Nov 14, 2024 · 0 comments · May be fixed by #3634

Comments

@ellykits
Copy link
Collaborator

Describe the feature request.
Reduce the amount of memory used by the app to hold register and profile data

Additional context
The application logs several Garbage Collection content each time a register/profile is launched. Reducing these logs would require fixing memory issues.

Acceptance criteria
Reduced number of GC logs
Expected performance gain; reducing the GC triggers

Area path
A list of ordered steps in the app on usage of the feature to support anyone testing it e.g. Code reviewer, QA e.g.

  1. Login to the app
  2. Open Navigation bar
  3. Click on _ any register_
  4. Observer quite a number of GC logs

Implementation plan (For Engineers)
Refactor Register/Default repositories to:

  • Reduce the number of object allocations
  • Use memory-efficient Data Structures
  • Re-use singleton object etc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment