-
Notifications
You must be signed in to change notification settings - Fork 292
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
Query caching for "sticky" scenes (plots, text logs...) #374
Labels
enhancement
New feature or request
📉 performance
Optimization, memory use, etc
⛃ re_datastore
affects the datastore itself
🔍 re_query
affects re_query itself
user-request
This is a pressing issue for one of our users
Milestone
Comments
teh-cmc
added
⛃ re_datastore
affects the datastore itself
🔍 re_query
affects re_query itself
📉 performance
Optimization, memory use, etc
labels
Feb 28, 2023
Also applies to the |
We're finally getting started on this now, though a fix will not likely land before December 2023. |
4 tasks
teh-cmc
added a commit
that referenced
this issue
Jan 23, 2024
Implement range invalidation and do a quality pass over all the size tracking stuff in the cache. **Range caching is now enabled by default!** - Fixes #4809 - Fixes #374 --- 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 - #4851 - #4852 - #4853 - #4856
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
📉 performance
Optimization, memory use, etc
⛃ re_datastore
affects the datastore itself
🔍 re_query
affects re_query itself
user-request
This is a pressing issue for one of our users
Currently, querying a sticky scene is O(n), and as time goes on it gets more and more laggy.
This is already an issue for plots and text logs today.
Ideally, one would want to cache the results of a query up to
now()
, and then only query the difference the next frame, and so on and so on.Problem is: what about out of order data?
The text was updated successfully, but these errors were encountered: