This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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
After a call with Shyam we better understand the challenge - that it's user's writing their own AI agents, which are in turn calling LSF and generating additional load.
We will consider this in future work
As LSF uses a proprietary protocol it is challenging to provide any form of traffic shaping. This is why lsfproxyd was introduced for very large clusters.
However, LWS is a rest api over http/https. As such, industry standard mechanisms to be used - such as load balancing and traffic shaping. For example:
Nginx: limit_req and limit_conn modules
Allows per‑IP request rate limiting
Supports burst handling and queueing
Can return native HTTP 429 responses
Apache HTTPD: mod_ratelimit, mod_evasive, mod_security
Controls request throughput
Detects abusive patterns and throttles or blocks clients
HAProxy: stick‑tables for rate limiting
Very efficient at connection‑level and request‑level throttling
Can enforce global or per‑client quotas
As such, we have no plans to add a proprietary mechanism.