vuu
vuu copied to clipboard
A way to avoid calling ignite cache too often for quick queries
should also not bother calling ignite for data when total rowcount is 0
@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?