Posts

Since TM1 is a memory-based OLAP engine, one of the most important considerations in developing  efficient planning models is to utilize the least amount of memory that is available on the server. As time goes on the model will likely grow in size and consume more resources. This usually happens when you add additional elements the cube’s dimensions and archive fewer elements . As the cube reaches its memory limit, users may experience issues like poor application performance, longer server start times, crashes, and other similar problems. Also, adding new elements can multiply memory use further because rules may act upon the elements added and take up even more of the server’s available resources. Read more

Many TM1 users have cubes with rules associated with historical data or completed plan versions and are needlessly recalculating their data on a continuous basis. This creates an unnecessary performance drain, and to make matters worse, what happens when the business rules change? Do you change history? Do you make rules overly complex by adding a time or version component to all of your rules? Using a few simple steps, this data could be “frozen” or made static, resulting in faster response time, less RAM consumption, and alleviating issues when business rules change. In this article, we will explain how to go about freezing this data. Read more