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.

Sign up for GitHub

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

Jump to bottom

Cache optimization #81

Closed
sorunokoe opened this issue Nov 4, 2024 · 2 comments
Closed

Cache optimization #81

sorunokoe opened this issue Nov 4, 2024 · 2 comments
Assignees
@ekazaev
Labels
enhancement New feature or request

Comments

@sorunokoe
Copy link

By scrolling chat upwards cache will increase in size (screenshot attached).

Screenshot 2024-11-04 at 10 50 52 Screenshot 2024-11-04 at 10 57 42
@ekazaev
Copy link
Owner

ekazaev commented Nov 18, 2024 •
edited
Loading

@sorunokoe Hi, Sorry. I dont get this issue. Can you provide more details please?
In general there is nothing wrong with having 530 objects in the cache. It is a cache. LayoutAttributes is a small object. A few string objects are probably occupying more memory than this entire cache. I do not see any reason to onptimise anything there. The question is if they should be there. Do not forget that this graph shows you all the layout attributes that currently exist. Only collection view itself at every moment holds 3 copies of the current state for internal calculation. You have to provide more details.

@ekazaev ekazaev self-assigned this Nov 18, 2024
@ekazaev ekazaev added the enhancement New feature or request label Nov 18, 2024
@ekazaev
Copy link
Owner

ekazaev commented Dec 3, 2024

@sorunokoe Closing due to inactivity

@ekazaev ekazaev closed this as completed Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ekazaev ekazaev

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ekazaev @sorunokoe