Page 1 of 1

Cubeview and Sub Editor frozen intermittently

Posted: Tue Oct 18, 2011 10:29 am
by harrytm1
hi all,

Users have been complaining about performance issues since the deployment to production. To determine whether it is a case of bandwidth issue, I access TM1 directly in the TM1 application server. At the same time, I also opened Task Manager to track the CPU and RAM utilisation.

I opened a cube view and it seemed fine. However, when I continued to open Sub Editor or even simple actions such as closing a cubeview or selecting an element from a title dimension, the entire Server Explorer froze intermittently.

Whenever that occurred, I noticed the CPU usage was around 5 to 20%.

Frankly, I have not experienced such incidents in other implementations. FYI, it is using 9.5.2 but not the latest FP1 version. There is 32GM RAM and the CPU speed is 2.39GHz. Total RAM used by TM1 is 10GB.

Any idea what's the cause? Any TM1 parameter that can cause this? It is using the following:
CheckFeedersMaximumCells=1000000
ReevaluateConditionalFeeders=T
AllowSeparateNandCRules=T
AllRuleCalcStargateOptimization=T
PersistentFeeders=T

Thanks for your attention.

Re: Cubeview and Sub Editor frozen intermittently

Posted: Tue Oct 18, 2011 5:35 pm
by John Hammond
Only time I saw this happening without it being a comms problem which you have eliminated by running on server is:

1. Cube is load on demand or has been unloaded.
2. TM1 space has been swapped out to disk and you have the wait till the pages return.
3. TM1 is running on a VM that does not have enough resource.
4. Anti Virus (esp Not on and Mc Crappy) being overzealous ( disable temporarily to check if this is the case)

HTH though this is me clutching at straws as you have done everything right to diagnose the problem.

Re: Cubeview and Sub Editor frozen intermittently

Posted: Wed Oct 19, 2011 1:59 am
by harrytm1
Thanks for the reply. From my reply below, Item 4 is the only one that I can work on.

Anyone else has any experience on this?

1. Cube is load on demand or has been unloaded.
They are not set to load on demand.

2. TM1 space has been swapped out to disk and you have the wait till the pages return.
The model takes up 10GB RAM out of max 32GB RAM. The other apps are not utilising much RAM, so I doubt it is due to swapping. Pls correct me if my understanding is incorrect.

3. TM1 is running on a VM that does not have enough resource.
The server is not running on VM. It's a physical server.

4. Anti Virus (esp Not on and Mc Crappy) being overzealous ( disable temporarily to check if this is the case)
I will check on the type of anti virus s/w and try to disable it to see if performance is better.

Re: Cubeview and Sub Editor frozen intermittently

Posted: Wed Oct 19, 2011 2:17 am
by rmackenzie
harrytm1 wrote:I opened a cube view and it seemed fine. However, when I continued to open Sub Editor or even simple actions such as closing a cubeview or selecting an element from a title dimension, the entire Server Explorer froze intermittently.

Whenever that occurred, I noticed the CPU usage was around 5 to 20%.
It makes a big different what process was using the 5-20%.

If it was the TM1 executable (tm1sd.exe or tm1s.exe) then you ought to be able to use TM1 Top to analyse what activity is causing performance headaches and the intermittent freezing in your Server Explorer. For example, one easy explanation is that there is a chore running every N minutes that disrupts normal user activity. Have you checked for that?

On the other hand if TM1 isn't actually doing anything then you do have a puzzling situation. Once again, the key would be to analyse for which process the CPU usage spike occurs in order to find the cause of the disruption. If it is e.g. norton.exe then you have a good start point for fixing the problem!

Links to TM1 Top documentation on the internet are here and here.

Re: Cubeview and Sub Editor frozen intermittently

Posted: Wed Oct 19, 2011 7:54 am
by John Hammond
One more and this is a left field thing:

Hardware failure intermittent then repaired for both memory and disk will give the behaviour you describe however with modern servers and specialised support this should nt happen.

(But as we all know the PR provided by Outsourcing companies that you are running on superb hardware maintained by elite techies is complete Ibollix and it may be worth a look at the logs and RAID to see if something has crept under their radar).