Unexpected Model Size Increase After Updating Custom Time Range

sosunkwo · 2025-02-04T15:50:32+00:00

There was an error rendering this rich post.

Hi Anaplan Community,

I recently updated a custom time range in my model and noticed an unexpected increase in model size.

Previously, my custom time range started in FY22 with 4 periods, and the total model size was 78 GB.

After updating the start period to FY23 (keeping the number of periods at 4), the model size increased to 87 GB instead of staying the same.

I expected minimal change since the number of periods remained constant. Has anyone experienced a similar issue, and what could be causing this increase? Could it be related to hidden data retention, formula recalculations, or Anaplan's memory allocation behavior?

Any insights or recommendations on how to find the root cause of this size increase OR how to reduce the model size after such changes would be greatly appreciated!

Accepted answers

rob_marshall

@sosunkwo

Great question…Let me ask you a question, are you using Native Versions with Switchover with this time range? If so, that makes sense because you now have more "out" time periods than before. Before the change, you had more "Actual" data and therefore the system referenced those periods (not counting them). With the more forecast data (non Actual), the size of the model should increase.

All comments

rob_marshall

@sosunkwo

sosunkwo

@rob_marshall,

Ah I get it! And yes, we do in fact have a good number of modules using the native Versions (with Switchover) with this time range.

Well noted. We are now exploring ways to optimize the model post size increase. Thanks, Rob!

andrewtye

@rob_marshall always having the answer! 👍️

rob_marshall

@andrewtye just trying to keep up with you!

MattiaLietaert

@sosunkwo I have the same issue. Have you found ways to optimize the most model size increase? If so, would you mind sharing them?

sosunkwo

Hi @MattiaLietaert - here are some steps we took (& are still taking):

Disable unnecessary summaries in line items.
Identify modules where a list subset can be used (especially if there is a big difference between the full list vs what the module needs).
Trim down the scale of our time ranges - we found that for some time ranges, we could shave off one or two years without impacting our downstream reporting/modeling.
Clean up our lists - there were many list items that were no longer needed. So, we deleted those.

I hope this helps. If you discover more ways to get back workspace, please share :)

Quick Links

Can you help?

Unanswered questions

Not Able to Join the Level 1 Model Building Course
Hey Everyone, I was trying to learn about the Level 1 Model Building Course, when i log in to my system and click on "Start the course" option its showing training unavailable, Can anyone please help me with this @Dikshant and all?
Generating Failure Dump - even though no warnings/error in Actions
I've few actions in our Supply model which when run takes some time on the "generating failure dump" step at the end of the action even though the import is a full success without warning or errors. This is just a few seconds when run for a single action, however we have a process with 120 actions, and most of these…
OAUTH 2.0 vs Google Sheets Extension
Hi, My org is looking to explore leveraging Google Apps script to extract data out of Anaplan and update already built templates in Google Sheets. We use the Anaplan Extension currently but find it crashes often with the amount of tabs, data, etc. Has anyone used both Anaplan OAUTH 2.0 API and Goolge Apps Script to write…