Exploding memory requirement with C8

[Hevex]

Hi All,

Could you please help me to understand why TM1 will have no problem displaying values in a cube viewer, but comes to a halt if the same
type of query is asked through Cognos 8 BI's report studio? One of our dimensions has 30,000 elements, which is not an issue in CubeViewer,
but causes C8 reports run for an hour.

Monitoring the the box where our TM1 9.4 resides I've noticed that the memory usage hardly changes through cubeviewer interaction, but would quadruple if a simple drill down is required in C8. Also I do not understand while the page file keeps expanding as well?

Thank you for your help
Z

[MarioRubbo]

I've had the same issue with a really big dimension in TM1 exposed through C8. I was never able to find a fix. I tried adding artificial hierarchy levels to make it easier to digest by C8 but it continued to choke.

[David Usherwood]

I have heard rumours of performance and scalability challenges with TM1 and C8, but didn't find issues when I tested, albeit in a small way. It's likely that the MDX-based approach used by C8 struggles with pulling large dimensions across - I'll try it when I have a moment.
You could consider using security to restrict what users see.

[Kyro]

I suggest putting TM1 on the same box as C8 BI to test the impact your network is having.

[Hevex]

Hi All,

I have upgraded C8 BI to 8.4.1 and loaded Fix Pack 1, which seem to solved majority of the issues!
Performance is much better when quering big dimensions.

Thank you
Z