IBM Data and AI Ideas Portal for Customers


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:

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

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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Workspace Spectrum LSF
Created by Guest
Created on Mar 31, 2021

Set a limit in the MC receive queue

TSMC is using MC to balance work load between clusters. When the submission cluster is busy, it forwards some jobs to execution clusters. The execution cluster has it's own workload except the forwarded jobs. To avoid the forwarded jobs occupy most of the resources of the execution cluster, we need to limit the slots occupied by the forwarded jobs.
We considered set a limit in the receive queue like the example shown below. The recq queue can have at most 100 jobs in RUN, USUSP and SSUSP status.

========================
Begin Limit
NAME = transfer_queue_jobs
JOBS = 100
QUEUES = recq
End Limit

If the receive queue is not dedicated to receive jobs from remote cluster or it can receive jobs from different remote cluster, you can use other consumer types to constrain it. The consumer types are listed below:
• Applications (APPS or PER_APP).
• Queues (QUEUES or PER_QUEUE).
• Hosts and host groups (HOSTS or PER_HOST).
• Users and user groups (USERS or PER_USER).
• Projects (PROJECTS or PER_PROJECT).
• LSF License Scheduler projects (LIC_PROJECTS or PER_LIC_PROJECT).
===========================

However, because the receive queue app/user/host/queue/project are all not special identity, so this solution is not worked.