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 (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,

  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 (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


ADD A NEW IDEA

Search results: Scheduling

Showing 16 of 1578

Do not start jobs with less than X cores per host

It is useful for when ptiles or slots do not fulfill your needs. Using an example, we have an MPI code that requests 100 cores. We don't tell LSF how to grab those cores, and sometimes it will go out and span across 12 nodes, taking 19 cores on on...
5 months ago in Spectrum LSF / Scheduling 0 Future consideration

Group jobs to same cluster when using bsub -cluster feature

Goal: Group together lsf jobs, "regression", in such a way that bsub -cluster feature directs all jobs in the group to the same cluster. Proposal: a) bsub submits all jobs in a job array to a single cluster bsub -cluster all -J "ArrayName[1-10]" /...
over 1 year ago in Spectrum LSF / Scheduling 1 Delivered

job select statement improvement

I have hosts with exclusive resources and some with a dynamic resource. A few hosts have two exclusive resources. The job submit: $ bsub -R 'select[ defined(res1) || (defined(res2) && dynamic_pool==loaner_host)]' I would expect this job to...
about 3 years ago in Spectrum LSF / Scheduling 2 Future consideration

Multiple queues request for job - consider taking in account queue limitations and lsf.resources for better job dispatching.

Today, when we submit a job with multiple queues (bsub "high risk") The job will be dispatched to a relevant queue by examine parameters such as queue status(open/closed), queue hosts, time-limit. In a situation, where a queue "high" have a ujob_l...
about 1 year ago in Spectrum LSF / Scheduling 1 Not under consideration

Array job maximum running jobs should be honored across multiclustered environments

Our users submit array jobs, but due to many factors may want to limit the number of running tasks at a time, not only from the source cluster, but total running jobs of that array for all clusters involved ( we have many clusters that use multicl...
over 1 year ago in Spectrum LSF / Scheduling 0 Delivered

Run LSF file IO operations within the container.

LSF jobs using containers depend on mounts within the container. These mounts are not available on bare metal where LSF runs file operations. The bare metal dependency means that LSF file related operations, -o, -f, -E, -Ep, etc. will not have acc...
over 1 year ago in Spectrum LSF / Scheduling 1 Delivered

Correct on Design Flaw in Session Scheduler

Currently the Session Manager and Service Director operate in the same CGROUP on the first execution host which causes a race condition that if a task on the first execution host pushes the memory use above the memory limit (aka mem-eater process)...
over 1 year ago in Spectrum LSF / Scheduling 1 Not under consideration

Reporting both host-based pending reason and main pending reason

"LSF does not support reporting both host-based pending reason and main pending reason (about license)." Let me provide a portion of the bsub statement from our case to exemplify the customer's dilemma. bsub -R "rusage[mem=3000.00:duration=1m,md_r...
over 3 years ago in Spectrum LSF / Scheduling 1 Not under consideration

Affinity support for windows compute servers

We have a mixed Linux/Windows cluster. Unfortunately the affinity string in the resource requirement is not supported on Windows. This leads to several problems: 1. jobs with affinity settings will not be dispatched to windows nodes 2. less perfor...
about 2 years ago in Spectrum LSF / Scheduling 1 Future consideration

Use all applicable NUMA Memory information on a machine to determine available Memory resources before dispatching a job to a machine

We were noticing that jobs were being terminated by LSF with the message: TERM_MEMLIMIT: job killed after reaching LSF memory usage limit.Exited with exit code 137. Yet, this was happening before the job had even consumed the amount of memory rese...
about 2 years ago in Spectrum LSF / Scheduling 0 Planned for future release

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.