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

A way to avoid calling ignite cache too often for quick queries #1225

Open
Tracked by #1196
naleeha opened this issue Feb 23, 2024 · 1 comment
Open
Tracked by #1196

A way to avoid calling ignite cache too often for quick queries #1225

naleeha opened this issue Feb 23, 2024 · 1 comment
Labels
Bigdata server

Comments

@naleeha
Copy link
Contributor

naleeha commented Feb 23, 2024 •
edited
Loading

should also not bother calling ignite for data when total rowcount is 0
@naleeha naleeha mentioned this issue Feb 23, 2024
Open
@naleeha
Copy link
Contributor Author

naleeha commented Mar 1, 2024 •
edited
Loading

@chrisjstevo had one idea which was to use something similar to LogAtFrequency (currently in the code base to log at certain intervals)

It is a good option but i dont think we can call something similar in the IgniteOrderDataProvider because one instance of this is shared across multiple instances of the VirtualizedSessionTable

Might be a good opportunity to refactor the common code for VP/table related code that is not specific to order & how you source the data to something like VirtualSessionTableUpdater which we create a new instance of per new instance of VirtualizedSessionTable?

@naleeha naleeha moved this to 📋 Backlog in Vuu board Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bigdata server
Projects
Vuu board
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@naleeha