Suggestion for Data Pipe lining
Suggestion for Data Pipe lining
Mairaj
Posts: 4Questions: 1Answers: 0
I have a confusion about pipe lining feature.
I have say 9 pages and i set 3 pages to cache so 3 pages are cached now when i go to page 4 again a request i sent to server that is fine as well.
But now if i click page 1 again a server call is sent my question is why this call is sent as this page was cached already ?
This discussion has been closed.
Replies
It isn't already cached. Once you load page 4, the cached pages are 4,5,6. The old cache is erased.
It would be possible to modify the pipeling code do do what you are looking for if you wanted to do so.
Allan
Ok so don't you think the pages already cached should remain in cache so this will improve the performance ?
It is an option. It is a trade off between that and memory consumption. The more pages you load, the more memory required of course. So yes, your suggestion is perfectly valid, but equally so is the current implementation
.
Allan
Ok thanks.
I guess you can add an option whether to cache pages which are loaded at least once or only cache specific number of pages so developers can choose what they see fit.
Please close this discussion.
I started out with the provided pipeline code and rewrote mine to be able to hold onto the data once it is cached. As Allen pointed out, you need to know the worst case before implementing something like this. Another possibility is to cache to a certain limit, say a 1000 rows, for example.