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
Workspace Db2
Components pureScale
Created by Guest
Created on Oct 27, 2014

pureScale async duplexing to secondary CF

CMB is planning to use GDPC in 2 sites which distance is about 50km. The round-trip response time is about 400 microseconds, so the delay on transfer to 2nd CF is too expensive.
  • Guest
    May 29, 2019

    Closing this idea off as there is no response to further clarify the issue.

  • Guest
    Apr 2, 2019

    At 50KM between the two GDPC sites, the workload needs to be read-mostly to have reasonable performance.  With that distance, have the high response time is not unreasonable.  The duplexing of data to secondary CF is only part of the concern, there are other commands to the CF that will likely be impacted.   And because the primary CF can be on either side and the app that drives the write that needs to go to both CF can be from any side, there is no guarantee removing the duplex (if we are able to) will address the problem because the time it takes to go to the primary CF on the other side will also take 400 microseconds.   It is important to understand the expectation of the workload to ensure it can be met by the configuration.