Model Load, Save, and Rollback

Model Load:

A large and complex model such as 10B cells can take up to 10 minutes to load the first time it's in use after a period of inactivity of 60 minutes.

The only way to reduce the load time is by identifying what formula takes most of the time. This requires the Anaplan L3 support (ask for a Model Opening Analysis), but you can reduce the time yourself by applying the formula best practices listed above.

One other possible leverage is on list setup: Text properties on a list can increase the load times, and subsets on lists can disproportionately increase load times. It is best practice not to use List Properties but house the attributes in a System model dimensioned by the list.  See Best practice for Module design for more details.

Model Save:

A model will save when the amount of changes made by end-users exceeds a certain threshold. This action can take several minutes and will be a blocking operation. Administrators have no leverage on model save besides formula optimization and reducing model complexity. Using ALM and Deployed mode increases this threshold, so it is best to use Deployed mode whenever possible.

Model Rollback:

A model will roll back in some cases of an invalid formula, or when a model builder attempts to adjust a setting that would result in an invalid state. In some large models, the rollback takes approximately the time to open the model, and up to 10 minutes worth of accumulated changes, followed by a model save.

The recommendation is to use ALM and have a DEV model which size does not exceed 500M cells, with a production list limited to a few dozen items, and have TEST and PROD models with the full size and large lists. Since no formula editing will happen in TEST or PROD, the model will never rollback after a user action. It can roll back on the DEV model but will take a few seconds only if the model is small.

The content in this article has not been evaluated for all Anaplan implementations and may not be recommended for your specific situation.
Please consult your internal administrators prior to applying any of the ideas or steps in this article.
Comments

@DavidSmith wrote:
  Model Save:

A model will save when the amount of changes made by end-users exceeds a certain threshold. This action can take several minutes and will be a blocking operation. Administrator have no leverage on model save besides formula optimization and model size reducing. 


Enhancement request: can the message in the blue box be updated to inform users that the blocking action is saving the model? To the layperson, it is not apparent why a blocking action is taking place. It would help as an administrator to know: 1) the blocking action is due to model save 2) reduce model size and optimize formulas to reduce model save time.

@DavidSmith: thank you for the informative post!

 

Can you provide some additional insight on how model saves work, and some statistics to give us an idea of how long we should expect typical FP&A models to save? For instance, if the standard FP&A model on the App Hub takes 30 seconds to save, and a model of comparable size that we've built with a client (or that a client has built) takes 10 minutes to save, it would tell us that we need to take a look at our formula complexity, and not necessarily model size. Similarly, it would help us set and manage expectations with clients that the model may be unavailable for a few minutes, periodically.

Labels (2)
0 Kudos