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 Future consideration
Workspace Db2
Components pureScale
Created by Guest
Created on Dec 15, 2021

Decreasing CF memory is slow

While working with PureScale, there may be a need to create room for new DB in the system. Once this happens we need to reconfigure CF memory, while keeping system up and running.

We are concerned regarding CF_MEM_SZ , CF_GBP_SZ and CF_DB_MEM_SZ, which we can not decrease online even though those parameters are configurable online.

Sample command that results in timeout:
db2 update db cfg for prdind using CF_GBP_SZ 5243120 immediate
SQL2046N The configuration parameter named "Cf_gbp_sz" could not be updated
because the operation timed out.

Note that timeout above happens as the value we try to decrease is too large. If we try to reduce in small steps, command works fine.

Based on our analysis, it is difficult to shrink a structure. Shrinking requires moving memory around depending on many factors like de-fragmentation, workload (latch contention), potentially more factors. This is why the automatic CF memory tuner always shrinks in very small increments like 1MB. There is no guarantee that a structure can be shrieked to any value within a given time limit. Especially GBP because its always in use during a workload.

To be able to shrink a structure more effectively, we have decreased in small chunks. This is time consuming, and if we need to release many gigabytes, it can easily take many hours with current behaviour.

We also considered castout that can be configured to be more effective, so that pages can be freed in the GBP so that they can be re-used. This configuration is related to GBP castout (page_age_trgt_gcr), however this parameter has performance impact, and difficult to modify in PROD.

Yet another alternative is to consider offline change for CF memory, to create room for restore test faster. However this does not maintain HA as we need to bring CF offline.

Can we get a design change, so CF memory can be tuned more effectively, and entire PureScale solution is more robust and user friendly?

Needed By Quarter