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 (https://ideas.ibm.com).
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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
In a system with more one NUMA node sometimes best to have all memory allocated on the first NUMA node for performance.
E.g. With 2 NUMA nodes with 300Gb each, pin the lowest number CPU VPs pinned to the first NUMA node and allocate all hugepages on the first NUMA node. As the lowest number CPU VPs are used most, this ensures most memory references are local.
However update statistics can require large amounts of memory for sorting.
If only memory on the first NUMA node is used and the first NUMA node does not contain enough memory the update statistics can generate
large spills to temp e.g. 100GB for some tables.
If memory is allocated on multiple NUMA nodes there is currently no way to control which numa nodes are used for memory allocations.
It would be best if user sessions can be guaranteed to allocate memory from the first NUMA node as normal and only the update statistics
allocates memory from the 2nd NUMA node rather than spilling to temp. This would avoid 100GB spills to temp with associated i/o impact.
With this in mind the following onconfig extensions are suggested:
# Default numa node for memory allocated included user sessions
# Control how memory from the virtual portion is allocated across NUMA nodes.
Do not place IBM confidential, company confidential, or personal information into any field.