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

Primary cache: size statistics & mem panel #4730

Closed
teh-cmc opened this issue Jan 8, 2024 · 0 comments · Fixed by #4773
Closed

Primary cache: size statistics & mem panel #4730

teh-cmc opened this issue Jan 8, 2024 · 0 comments · Fixed by #4773
Labels
🧑‍💻 dev experience developer experience (excluding CI) 🔍 re_query affects re_query itself

Comments

@teh-cmc
Copy link
Member

teh-cmc commented Jan 8, 2024

The primary cache should implement SizeBytes and expose all its stats to the memory panel.

@teh-cmc teh-cmc added 🧑‍💻 dev experience developer experience (excluding CI) 🔍 re_query affects re_query itself labels Jan 8, 2024
@teh-cmc teh-cmc changed the title Implement primary cache size statistics Primary cache: size statistics & mem panel Jan 8, 2024
teh-cmc added a commit that referenced this issue Jan 15, 2024
)

The primary cache now tracks memory statistics and display them in the
memory panel.

This immediately highlights a very stupid thing that the cache does:
missing optional components that have been turned into streams of
default values by the `ArchetypeView` are materialized as such
:man_facepalming:
- #4779


https://github.com/rerun-io/rerun/assets/2910679/876b264a-3f77-4d91-934e-aa8897bb32fe



- Fixes #4730 


---

Part of the primary caching series of PR (index search, joins,
deserialization):
- #4592
- #4593
- #4659
- #4680 
- #4681
- #4698
- #4711
- #4712
- #4721 
- #4726 
- #4773
- #4784
- #4785
- #4793
- #4800
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧑‍💻 dev experience developer experience (excluding CI) 🔍 re_query affects re_query itself
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant