Skip to Main Content
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 Not under consideration
Created by Guest
Created on Jan 11, 2022

Rearchitect the colgroup processing to be more granular using multiple sorts as opposed to a single sort or more intelligently avoid the colgroup sort altogether (when possible)

Looking at the job output you sent in, we can see that there are 18 colgroups specified.

Based on the current design, we have a single sort for colgroup(s).

There are 184310123 rows unloaded

The no. of the rows passed to the single

dstats sort pipe is equal to 18 x no. of records inside the tablespace.

This may take a long time to do the sort.

There is no easy way to fix this scenario based on the current design.

You can choose to reduce the amount of data being collected and processed by

specifying less the number of colgroups.

As a future enhancement we need to rearchitect the colgroup processing to be more granular

using multiple sorts as opposed to a single sort or more intelligently avoid the

colgroup sort altogether (when possible). You can open an AHA request on this.

Needed By Quarter
  • Admin
    Megan Yee
    May 6, 2022

    Thank you for submitting this enhancement request. While we view all the enhancement requests we receive as valuable and we would like to implement all of them, in an effort to have maximum transparency we are closing the ones that don’t currently appear on our two year product roadmap.

    We have chosen to decline this request at this time for the following reasons:
    The suggested re-architecture of the colgroup processing is a large development effort and would require delivery in a release boundary with significant changes. Instead, we are working towards a long-term solution to improve stats profile processing to reduce the necessity of generating a large number of colgroups.