TM1 10.1 64 Bit and Excel 2007
Architect
Do loading aliases have an impact on performance? I have a dimension with 374,456 elements and all have an alias. The element is the AR Customer Number and the AR Customer Name is the alias. I have looked through the Install and Config User Guide and located a parameter on the tm1s.cfg file called SkipLoadingAliases. It seems to imply that if you don't load the alias load time of the cube might be improved possibly. I don't want to turn off the loading of my aliases however if this does impact performance I could give my AR department a better understanding of why the cube errors and a maximum memory box appears when they expand the AR Customer dimension to the 0-level. I tested the SkipLoadingAliases in a development environment however it didn't seem to help performance of the cube.
Memory Used for Views 0
Number of Stored Views 0
Number of Stored Calculated Cells 0
Number of Populated String Cells 0
Number of Populated Numeric Cells 10400891
Number of Fed Cells 0
Memory Used for Calculations 0
Memory Used for Feeders 343932928
Memory Used for Input Data 427824128
Total Memory Used 771757056
Alias Impact On Cube Performance
-
- Posts: 31
- Joined: Thu Apr 25, 2013 1:36 pm
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2007
-
- Community Contributor
- Posts: 349
- Joined: Tue Aug 17, 2010 6:31 am
- OLAP Product: Planning Analytics
- Version: 2.0.5
- Excel Version: 2016
Re: Alias Impact On Cube Performance
You could also try changing the view size and timeout settings so users don't get errors when expanding down to that level. It would also depend on the number of n level elements under each c level item as well I believe.
-
- MVP
- Posts: 2836
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: Alias Impact On Cube Performance
Your issue has nothing to do with aliases. If you have a 300,000+ member dimension and you are trying to display a cube view with that dimension on either the rows and columns, and have all the leaf elements in the view, you are going to get errors. Neither Architect or Perspectives is going to be able to handle a cube view with that many elements. You will have to filter the dimension down to a smaller subset or break it up via mid-level parental hierarchy.
-
- Posts: 31
- Joined: Thu Apr 25, 2013 1:36 pm
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2007
Re: Alias Impact On Cube Performance
Thanks for the feedback. We have a redesign meet next week for this cube. I will bring these suggestion to the table. Appreciate it!
-
- MVP
- Posts: 3241
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.1.5
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Alias Impact On Cube Performance
Just a quick note when I see that you have a dimension with 374,456 elements.
Try to make changes to the dimension through TI, rather than through the user interface (Edit Dimension Structure).
That will be quicker and more stable.
Good luck with the redesign !
Try to make changes to the dimension through TI, rather than through the user interface (Edit Dimension Structure).
That will be quicker and more stable.
Good luck with the redesign !
Best regards,
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly