MaximumViewSize has no effect

Post Reply
holger_b
Posts: 131
Joined: Tue May 17, 2011 10:04 am
OLAP Product: TM1
Version: Planning Analytics 2.0
Excel Version: 2016
Location: Freiburg, Germany

MaximumViewSize has no effect

Post by holger_b »

We have this analysis cube with a set of really complex rules (which come along without any feeders). Right after system start this cube requires some 2 GB in memory, but when users start browsing, memory used for calculations can quickly jump up to 35 or even 50 GB.

MaximumViewSize is set to 5000, however the opening of such a vast view is never interrupted, be it in Perspectives or in PAW - any idea why? Works as expected with other cubes, but not with this one.
ascheevel
Community Contributor
Posts: 286
Joined: Fri Feb 15, 2013 5:49 pm
OLAP Product: TM1
Version: PA 2.0.9.1
Excel Version: 365
Location: Minneapolis, USA

Re: MaximumViewSize has no effect

Post by ascheevel »

You're conflating two separate things. The MaximumViewSize parameter is literally just the memory required to to hold the values in the view. To get to those values though, the server might need to evaluate/process rules on any number of cells behind the scenes which consumes memory but is not included in the total memory used for the view. That memory is just server memory (as limited by the size of your server)

Another way to think about it is to consider an income statement forecasting model whose sole purpose is to forecast net income. If you create a view with just net income by month for 12 months, the size of that view will be tiny (and governed by the MaximumViewSize), but almost all of the memory consumed by the server will have been to serve you that one measure. Make sense?
holger_b
Posts: 131
Joined: Tue May 17, 2011 10:04 am
OLAP Product: TM1
Version: Planning Analytics 2.0
Excel Version: 2016
Location: Freiburg, Germany

Re: MaximumViewSize has no effect

Post by holger_b »

Absolutely, yes. Actually that is what I thought the reason might probably be.

Thank you!
Holger
Post Reply