TM1 Server Restart

[Ajay]

Hi All

I have a noticed something odd when my TM1 server restarts and wanted to know if this is just happening to me or whether this is common for all.

Bascially when the server starts, Task manager suggests that only 13% of the CPU is being used. I have no other processes running so wondered why the full 100% wasn't being used. Obviously if it was it would speed up the load of the server.

Picture attached if any help

Regards
Ajay

[wissew]

TM1 can run in a multi-threaded mode. The hitch is you have to tell it to. The default is single threading or a single CPU. The tm1.cfg file has to include MaximumCubeLoadThreads="number of cpu to use". The catch is that if you do this conditional feeders won't work properly. From your attachment it appears you have 8 cpu cores on the server. You can go as high as 8, but I wouldn't. Try 2 or 3. After making the change you will need to restart the server for the cfg options to take effect. This will reduce the start up time of the server as well. Check the help guide for other options to use in the cfg file.

[Ajay]

Thanks Wissew

I think I maybe a bit unfortunate here as the documentation for our release appears not to show this configuration setting for the cfg file.

We are on 9.0 SP3 U7 but in the process of weighup an upgrade to 9.4 or dare I say 9.5

In addition the documentation on conditional feeders is not clear also. When we speak of conditional feeders I think that this is any statements below the "FEEDERS;" line in my rule where the right hand side of the feeder contains a conditional statement, like an "IF".

But I have seen some refer to this as any condition on the actual rule itself.

What is the correct definition of a conditional feeder ?

Ajay

[paulsimon]

Ajay

In addition the documentation on conditional feeders is not clear also. When we speak of conditional feeders I think that this is any statements below the "FEEDERS;" line in my rule where the right hand side of the feeder contains a conditional statement, like an "IF".

But I have seen some refer to this as any condition on the actual rule itself.

The conditional feeder option is nothing do do with rules, only feeders. It only applies where a feeder from A => B has a conditional part on the right hand side that refers to C. The problem is that feeders only fire when 'A' goes from zero to non-zero. If the value in 'A' stays the same, but the value of C changes, eg there might be a condition on the feeder like ['A'] => DB('MyCube',....., IF( DB('MyCube',....,'C') > 500,'Breach',''),.....'B') ; so the feeder is nullified unless C is over 500. If the value of C goes from under 500 to over 500 the feeder won't fire, as it is only looking at the value of 'A'. The TM1S.CFG setting ReevaluateConditionalFeeders=T is an attempt to make TM1 reevaluate conditional feeders when data changes. However, although I have used this option, it doesn't actually seem to work. The best approach is to redesign the system so that it doesn't need this sort of feeder, either that or be content to run a TI with a ProcessFeeders which will force re-evaluation of all feeders on the given cube.

We had a lot of problems with 9.4. I would go with 9.5. It seems to have most of the bug fixes that went in to 9.4 and some that haven't (yet) made it to 9.4. Secondly, unless you have already downloaded 9.4, IBM will only let you download the latest version anyway. Having said that I have only been working with 9.5 for a few weeks, so I haven't tested it out in production yet.

Regards


Paul Simon