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,
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
See this idea on ideas.ibm.com
So let's say a user is running a job that goes on for a couple of days. The CPU is active say every other 30 minutes, but idle most of the time. The CPU is active for 5 minutes but idle for 30 minutes.
I would like to know the time stamp as when was the last CPU activity.
That data point is update_time which exists.
The idea is not to kill a job if by convention means is deemed idle. In other words the CPU Time vs. Wall Clock time.
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.
Attachment (Use case): script that generates data on jobs that were last idling. The job goes in and out of idle states periodically.
The information can be viewed. I would like to view only those jobs that are idling beyond a certain time limit out of several thousand jobs. And take appropriate action whether to terminate them or not.
Attached is a script that drives the point home and can be easily converted into an alert.
In RTM today you can view how a job is consuming cpu over time - so you can see if a job is accumulating wall clock time but not cpu time etc (likewise, there is a feature in LSF (JOB_IDLE) which will invoke a script beyond a certain walltime/cputime ratio.
Can you clarify why the existing functionality is insufficient?
Creating a new RFE based on Community RFE #70697 in product Platform LSF.