Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Future consideration
Workspace Db2
Created by Guest
Created on Jan 20, 2022

Improved Db2 backup thread (db2bm and db2med) binding/distribution on NUMA systems

On a large NUMA systems with a very fast storage and a fast backup target memory affinity might affect backup time as well as the overall system performance during the activity.
Currently, with the Db2's automatic thread NUMA binding (DB2_RESOURCE_POLICY=AUTOMATIC), all backup buffer manipulator threads (db2bm EDUs) are affinitized with the same node on which backup coordinator agent was started whilst media controller EDUs (db2med) are bound to a different NUMA node. This behaviour is sub-optimal performance wise and might lead to a saturation of the CPU interconnects.
Db2 should be able to distribute backup threads across multiple NUMA nodes, preferably colocating db2bm, db2med pairs and ideally affinitize utility heap memory associated with those.

Needed By Yesterday (Let's go already!)
  • Guest
    Jun 24, 2022

    Hello IBM,

    We have some additional comments / clarifications regarding our previos request:

    1. For a backup done with the option "DEDUP" DEVICE the fixed db2med and db2bm pairs shall be bound to the same NUMA node.
      Since we have the DEDUP option set in our backup solution there should be a fixed 1:1 relationship between db2bm and db2med edus. We hope that under this specific scenario it would be possible and more easier for you to bind those threads to the same NUMA node ?
      We would appreciate if you could look at this option again and it is the most important request that would help us.

    2. For all other backup scenarios the db2med's and db2bm's threads shall be evenly distributed and bound to all NUMA nodes.

    Kind regards