The new page caching feature in Banzai (http://help.skuidify.com/m/supercharge-your-ui/l/428673-optimize-personalization-and-caching) sounds very promising, probably the most exciting part of the release for PractiFI.
I’ve been doing a little playing around with it, but can’t get my head around it just yet, so I have a few questions. My objective is to make our quite complex pages as blazingly fast as possible, whilst minimising the occurrences of stale data.
- What’s the technical difference between processing a model server side vs client side? If the models are processed client side, presumably the rest of the page XML is cached?
- How does caching work in conjunction with page includes? Are the contents of page includes cached? Should the included page itself have caching turned on, and its models set to load client side?
- Similarly, how does caching work in conjunction with tabs that are set to lazy load?
- Let’s say we have an account detail page in Skuid. Does caching speed up performance for every view of every account, or just every repeat view (within the timeout period) to a previously viewed account?
- Our Skuid pages are housed in Visualforce pages, and those Visualforce pages have caching turned on. That makes repeat views of previously viewed records super fast, but it creates problems with stale data (which we need to handle with clever model requerying in Skuid) and stale session cookies. If we use Banzai’s page caching to its fullest, I’m hoping we can turn off Visualforce caching. Does that sound feasible?