I have a C level rule in a cube with a ConsolidateChildren rule for the overarching parent to sum correctly the C level rule values below it. This is working fine in TM1 cube viewer and its performance is acceptable given the size of the cube (16 dimensions).
However, when using a tm1-ui-dbr function in Canvas, or a named mdx, to retrieve just the overarching parent value, it’s taking 10+ minutes to respond. I guess it has something to do with the way the API is retrieving the value but is there any way to overcome the performance issue?
Will probably need more information and further tests.
Can you help isolate by creating a single DBR and nothing else on the page, querying just a single cell and see if that is slow?
Do you have Pulse installed? Are you able to see what is executing or possibly any waiting threads in sessions?
If the named MDX is slow, there is a good chance that it is the API itself as the execution is already passed on to TM1 and is processed internally there. The next probable approach on the named MDX is to optimize that, as the query could be retrieving a lot of unnecessary members.