Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
This Techspert Talks session covers:
Chapters:
Resources:
Q&A:
Q: We have apps that are really big (13gb in RAM). It has a lot of data (number of rows approximately 150M). Where to start?
A: If the app analyzer will run, I would start there and then look for areas that could be reduced (e.g. Date fields, keys that can be autonumbered, etc.). If that does not work, I would suggest looking into reducing the amount of historical data the app contains (if possible), or moving towards an ODAG approach where users interact with a summarized set of data for the most part and spin up detailed apps of granular data when needed.
Q: We have an app more than 14 GB, how we can check with app analyzer?
A: If you have an application that is too large for the app analyzer, I would suggest reducing some of the history in order to be able to get the App Analyzer to run. The insights you will find should be applicable to the full data set.
Q: Does using Bookmarks as default on app open will reduce the load time for the app?
A: Yes, this is a great way to speed up the opening load time for end users.
Thank for the quick summary organization.