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:

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:

Status Planned for future release
Workspace Cloud Pak for Data
Created by Guest
Created on Apr 12, 2021

Slow running HPO jobs

We are seeing some latency on our platform when we submit a HPO job. When we submit a HPO job via WMLA we see that it is taking ~14 seconds to launch a trial in spite of asking number of parallel runs. Just to give you an idea, if we have latency of 14 secs for a model which runs in 100 secs…and a user submits a job asking for 100 parallel runs then latency adds substantial amount of time to the overall job execution. i.e. in theory, the job should have completed in 100 secs, but, with latency the job execution goes to 1400 + 100 secs.

Until now this had not been a problem because most of our workloads were model fitting that would go for hours, so a few seconds here or there wouldn't matter make a dent … but as we move onto simulations with relatively quick runtimes, this is becoming a big problem.

  • Guest
    Jun 30, 2021


    Is it possible to know when would this be available like an ETA.