This portal is to open public enhancement requests against IBM System Storage products. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
The GPFS memory footprint is defined by
- pagepool
- shared memory pool
- heap
- stack of all threads (512KB per GPFS thread, usually the stack size is not an issue)
"pagepool" and "shared memory pool" are configurable, but no parameter in GPFS to control the heap size. From OS view, we can use resource control to control the memory size of mmfsd (likes ulimit setting, the memory control subsystem of cgroup), the daemon will be killed by OS when mmfsd memory usage exceed the setting. That is not agood idea for GPFS to enforce the memory usage because of mmfsd died will impact the application and the whole setup.
The cache design doesn't work well in our case because of too many objects are cached and consume large number of memory space.
Idea priority | Medium |
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - IBM Spectrum Scale
Product - Spectrum Scale (formerly known as GPFS) - Public RFEs
Component - Product functionality
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - IBM Spectrum Scale
Product - Spectrum Scale (formerly known as GPFS) - Public RFEs
Component - Technical Foundation
We do not foresee this behavior being changed in the next few releases.
Clarification:
We guarantee our users a defined amount of memory on each compute node. Therefore it is mandatory to know and define the memory usage of GPFS.
In our setup we use only 8 GB pagepool. But we had to learn that in addition to the pagepool a dynamic memory is used. But this can't be limited.
We were faced a couple of times that the system healthchecker checked empty nodes and marked them as offline due to not enough memory is available.
It is not clear to me what problem you are asking us to solve. Can you describe more explicitly what behavior you want from Scale?
Can you please explain the problem to be solved?