I have a bit if a weird one were I have a cube of around 400MB and another of around 14GB. When using view construct for both cubes in both cases memory increases by 2GB???? Previously when they ran it it didn't behave this way. Memory went up but not to the extent.

Do you know if there is any difference (apart from unicode) between view construct in 9.1 and 9.5.2? How does it handle the out of page view selections?

Thanks in advance,

Jim.

Jim what exactly do you mean? ViewConstruct caches values in from the view in memory, nothing more. I don't think unicode is relevant (other than additional memory use in general), and what is "out of page view selection"?

"Internal testing comparing like tests comparing TM1 9.5.1 to TM1 9.5.2 with PI have shown the TM1 9.5.2 Server to allocate between 10 – 30% more RAM than the TM1 9.5.1 server. Some of this increased memory use is due to the internal structures created by PI, however the additional throughput of transactions – and their impact on View Cache – is also a contributing factor. IBM recommends planning for 30% more memory usage with TM1 9.5.2 than with prior versions of TM1."

It would be nice to know whether if PI is enabled in all the instances which are having this issue.

Do you know if there is any difference (apart from unicode) between view construct in 9.1 and 9.5.2? How does it handle the out of page view selections?

Thanks in advance,

Jim.

Jim what exactly do you mean? ViewConstruct caches values in from the view in memory, nothing more. I don't think unicode is relevant (other than additional memory use in general), and what is "out of page view selection"?

I know what it does so thanks for that. I also know what the impact of unicode is (which is why I put apart) so thanks also for that. When I say out of page view selections I mean the ones at the top that are not physically within the view page area were you have to have one element selected? Does that help? I can upload a screen dump if you like??

"Internal testing comparing like tests comparing TM1 9.5.1 to TM1 9.5.2 with PI have shown the TM1 9.5.2 Server to allocate between 10 – 30% more RAM than the TM1 9.5.1 server. Some of this increased memory use is due to the internal structures created by PI, however the additional throughput of transactions – and their impact on View Cache – is also a contributing factor. IBM recommends planning for 30% more memory usage with TM1 9.5.2 than with prior versions of TM1."

It would be nice to know whether if PI is enabled in all the instances which are having this issue.

It doesn't have PI enabled as it is a BI model and there isn't a great deal of writing going on. I good punt though and thanks.

jim wood wrote:.... When I say out of page view selections I mean the ones at the top that are not physically within the view page area were you have to have one element selected? Does that help? I can upload a screen dump if you like??

Only the title elements selected by index are included in the cached stargate view. It doesn't matter if a subset is assigned with other elements in it, if you want to cache for more than one filter element in one or more of the filter dimensions then you would have to cycle through by index and do more ViewConstructs.

If you are talking about the feature in TM1 Web and BI where you can have a filter/title dimension that isn't visible to the user then I am pretty certain that it would be treated the same as any other title element. I don't see how this could be any different since the view construct isn't something that happens on the UI level, it is just a background job to pre-calculate an array of values that belong to the view.

lotsaram wrote:Only the title elements selected by index are included in the cached stargate view. It doesn't matter if a subset is assigned with other elements in it, if you want to cache for more than one filter element in one or more of the filter dimensions then you would have to cycle through by index and do more ViewConstructs.

That pretty much covers it cheers. That's always what I understood to be the case but I was unsure whether it had changed down the version. Thanks.

Many thanks Moby. They are running the latest 9.5.2 hot fix pick install. They have not installed any hot fixes beyond the pack. As for the fixes / errors thanks for making me (and the community) aware of them but the issue we have doesn't directly correspond to either but it is close. You never know either fix may address the issue indirectly but just to clarify....

1) We are not unloading the cube before running view construct.
2) We are not running any other TI command other than view construct, so process feeders isn't applied.

I will however recommend to the customer that they apply the latest hot fix just in case,

Just a quick note to let you know that the development team have indentified this as an issue with the software. Neither of the fixes raised by Moby helped. A fix for this is due in the next FP which is slated for release in April. If however they manage to fix the issue before hand a hot fix will be released. Either way I will add the details to this post,