Hi Guys,
Zack: Noted. Thanks for the heads up.
For context, this post is related to Glenn’s previous post about cutting up a large page for performance. (https://community.skuid.com/t/how-to-structure-complex-related-pages-for-high-performa…).
A few months ago the page became unacceptably slow, so we implemented Zack’s earlier suggestion to cache the page in VF and to load model data asynchronously. This has definitely helped.
Notwithstanding this, we are rapidly running out of headroom so I’m exploring our options. Regarding Rob’s suggestion to use page includes- I’ve tried this in the past and found performance to be an issue. Additionally, splitting the page into multiple pages would have the added bonus of giving us back/forward buttons without implementing with history API- this is something we have wanted for a while and have not made time to do. Two birds with one stone as they say.
Thanks for your help and have a pleasant new years eve all,
Dan Arnison (PractiFI)
