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,
Post an idea
Upvote ideas that matter most to you
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.
In our cluster, we are very often impacted by jobs under reserving cpus (using -n option of bsub). for ex, we have a user group using a GUI for days. When the user close the GUI, it fires thousands of tar/bzip2 -9 to compress log files, making exec_host unresponsive for 10/15 minutes.
To limit cpu usage to the reserved number of slots, or a reasonable number of cores, we tried to use the affinity statement: it works but we cannot specify more cores than the number of cores available in the server. for ex, for a server having 40 cores, when specifying 8 cores per jobs, we cannot start more than 5 jobs for 120 slots avail on the servers (3 slots per core).
we also impacted by many GUI vendor tools that trying to use the max available cores on a server ignoring slots reserved in LSF. For servers shared by hundreds of peoples, it's very impactful.
Is it possible to change this behavior by allowing cores shared by jobs ?
Also, to improve this new behavior, allow load balancing between cores ?
Do not place IBM confidential, company confidential, or personal information into any field.