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 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,
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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
When shared memory segments are not using huge pages there can be performance impact
I would like an option for the engine to abort startup similar to FULL_DISK_INIT=0 if huge pages cannot be used for shared memory segments.
Scenario:
sysmaster sysscblst queries taking 2x longer with many connections when virtual shared memory segment is using standard pages.
On Linux shared memory segments have the shmkey set to 0 when the are destroyed.
If onstat/dbaccess (e.g. monitoring) sessions are still attached to those segments
the segments can hang around long enough they they are still there when the engine is restarted.
As the shmkey for the destroyed segments is 0 this will not clash with shmid's for the new engine.
However the new engine can fail to find the huge pages required and use standard pages for some segments.
Monitoring of online.log messages can find this but applications may have already connected and having to stop the engine again can be painful in environments with limited work windows.
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.