Re-Ordering of the dimensions (Views have become slow)

[dima55]

Hi All

i am facing a wierd problem in Re-Ordering of the dimensions , and would be thankful if someone can give me expert advice.

I took 2 cubes a and b. I checked the time taken for a view in both cubes to calculate and show the result. One cube gave me 14 min and the other 4.
After reodering i could save 700MB and 750MB of space. But the view for the 2nd cube has become extremely slow. The view which was taking 4 min is taking long time. I waited for about 20 mins than aborted the building of view. I did this for 2 - 3 times but with same results.

1.Could anyone tell why is this change in view and also what can be done to max the view speed
2.Also now that 1.4GB has been saved i thought the restart time will be saved. It saved only a min. Iniially it used to take 38 mins but now it is taking 37 mins.

Thanks
Dima

[dima55]

Hi All

Just wondering if this is a really easier one to figure out that the members here are letting me figure it on my own or a wierd one as i told that no one has encountered before to provide some advice.

I would be thankful if anyone can give any advice or just a hint how to figure this out .

Thanks
dima

[lotsaram]

Although there's a pretty good relationship between memory saved and faster recalculation performance on views it isn't necessarily 1:1 and also doesn't necessarily lead to performance improvement 10% of the time. It could be that yours is such a case, it is possible depending on calculation rules in place that performance could be slower even though cube size in memory is reduced, which is why you need to test following a re-order to see if not only memory consumption is saved but also calculation time.

[dima55]

Thanks lotsaram

i would have understood if the caculation time would be same or had increased say 1%-5% but this taking very long time which is really suprising . I dont know how to deal with it. this makes re -ordering feature a gamble

thanks
dima

[lotsaram]

i would have understood if the caculation time would be same or had increased say 1%-5% but this taking very long time which is really suprising . I dont know how to deal with it. this makes re -ordering feature a gamble

Gamble?
This is what D-Q-P is for ...
Would you completely change the indexing of a relational DB directly on production without testing first?

[dima55]

@lotsaram

TM1 includes a feature that lets you optimize the order of dimensions in a cube, thereby consuming less memory and improving performance.

When you optimize the order of dimensions in a cube, TM1 does not change the actual order of dimensions in the cube structure. TM1 does change the way dimensions are ordered internally on the server, but because the cube structure is not changed, any rules, functions, or applications referencing the cube remain valid.

This is what is said in the manual. I thought this will surely improve performance , even if it doesnt it will optmize space consumption without affecting anything else as said above. That makes me say that Re-order feature will consume less space but may or maynot improve performance also in somes cases makes performance worse.