IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Functionality already exists
Workspace Planning Analytics
Created by Guest
Created on Sep 28, 2020

Enable partitioning for .CUB and .FEEDER files

For very large (over 10GB) .cub and .feeder files, the time to load, save or process them could be substantially reduced were they partitioned and processed in parallel. For servers with 40 cores, the time savings can be significant.

The obvious use case is to partition by the Time dimension since historical time series data is generally static with only the current and future time periods changing.

During server startup, multiple partitions would be loaded in parallel, respecting the MTQ setting, for both cubes and feeders, even conditional feeders.

During a SAVEDATAALL, only the cube and feeder partitions that had changed would be saved and those would also be saved in parallel respecting the MTQ setting.

During a CubeProcessFeeders operation, the user would have the ability to specify the partitions to generate, or take the default option of ALL.

The benefits to customers is (1) increased application availability, (2) decreased load on network bandwidth during load/save/process feeder operations, and (3) opportunity to adjust the data backup/restore strategy to backup and recover only those partitions of interest.

Needed by Date Sep 28, 2020
  • Guest
    Feb 10, 2021

    With all due respect @Stuart King, no this functionality does not currently exist. The idea seems quite clearly and simply expressed as saving .cub and .feeder files for a single cube as MULTIPLE files rather than a monolithic file. The main benefit would be during a data save that only the partitions which had changed would need their files updated. This would lead to significant time saving and reducing locking when saving large cubes.

    This is clearly different from MTCubeLoad or MTFeeders.AtStartup. Yes these parameters boost performance during startup and they are a significant step forward. But they are very different from the main point of this proposed enhancement.

  • Admin
    Stuart King
    Feb 10, 2021

    Changed status to already exists. This is effectively what MTCubeLoad already does. We do not plan to allow cube and feeder files to be split into multiple files. This change would conflict with the longer term plan for disk storage of the TM1 model objects.

  • Guest
    Sep 28, 2020

    I support this idea