Planning Analytics using twice the memory of 10.1
-
- 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: Planning Analytics using twice the memory of 10.1
I'm guessing the css change is only going to be available to on-premise installations? We're going PA on the cloud this year and I would love to be able to alter the stylings for TM1web after we migrate.
- jim wood
- Site Admin
- Posts: 3958
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: Planning Analytics using twice the memory of 10.1
I can't see IBM giving you that level of access. May be on the partner cloud but not commercial, although they may be able to drop a CSS change in for you?
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Re: Planning Analytics using twice the memory of 10.1
Well, that's not really a challenge, I've been at it longer than most people in support. Glad it worked, happy to help

CSS changes would be only on-premise, but depending on the browser your organisation uses, you can add a plugin that would apply a custom skin to predefined url, allowing you to 'overlay' defaults with your organisation wide customisations. Something like Stylus
Cheers,
Y
Re: Planning Analytics using twice the memory of 10.1
I’ll just leave it here for anyone finding this thread later: another reason for memory growth is that PA is preloading all the views and subsets definitions on startup, whereas 10.2.2 didn’t do that. There will be a parameter in tm1s.cfg to disable this behaviour in future releases, but you can check whether this is your case by removing view files and restarting the server.
I wrote a post about this with more details
I wrote a post about this with more details