TM1 Forum

"When MaximumCubeLoadThreads is enabled, TM1 cannot manage the order in which feeders are calculated. There may be cases where processing order has an adverse effect on your application due to some order-of-evaluation dependencies in the multi-threaded environment."
I dont kown what is that , Any one had some instances or cases?

What are you asking about, exactly? If we use this parameter or if we've come across the issues described when it's turned on?

This parameter can speed up load times, especially if you have many computationally intensive cubes (large data volumes and/or many feeders).

However, this parameter should not be used (or used with extreme caution) if you have intercube feeders dependent on other feeders and/or if you use conditional feeders. Also, multithreaded load can cause TM1 to use significantly more (garbage) memory than single threaded load, so be cautious and run some tests with different settings.

per default tm1 server uses only ONE thread for starting up.
if you use rules with feeders these feeder calculations can be speeded up by changing the mentioned parameter, or you just use "PermanentFeeders" which gives a better performance boost for startup as long as it works and the feeder files are uptodate.

Martin Erlmoser wrote:"PermanentFeeders"

Persistent Feeders.

Ths All,i think i could understood.