Although, MTCubeload and MTFeeders.AtStartup have been around for some time now, I'm still trying to cement my understand on how exactly do they operate vs MaximumCubeLoadThreads. In particular its impact on conditional feeders.
It is well-known that MaximumCubeLoadThreads could not be turned on when conditional feeders were present, as TM1 engine could not control the sequence of how these feeders would be processed. Fair enough. Now, we have these two new parameters that leverage MTQ framework. IBM states that
MTCubeLoad also eliminates the risk of changing feeder generation sequences
Does this mean that data (raw or calculated) querying is now multithreaded, while feeder construction remains single threaded? Although, documentation For MTCubeLoad does not state anything in relation to conditional feeders, I'm making this assumption based on the fact that MTFeeders.AtStartup parameter needs to be set to F if there are conditional feeders in a model.
In the nutshell, I'm trying to understand what impact MTCubeLoad has on feeders, whether conditional or not. If we don't have conditional feeders, would MTCubeload leverage MTQ framework during feeder processing? Or do we still need to include MTFeeders.AtStartup? If we do have conditional feeders, would MTCubeLoad be smart enough to recognize that and turn disable MTQ for feeder processing?
Conditional Feeder = MTCubeLoad On + MTFeeders.AtStart Off ?
Regular Feeders = MTCubeLoad On ? Or MTCubeLoad On + MTFeeders.AtStartUp On?
Hope it makes sense!
Look forward to your ideas