Skip to Main Content
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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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

Status Submitted
Workspace Analytics Engine
Created by Guest
Created on Feb 20, 2024

Distributing  various files like spark events, spark job logs,  across pvcs.

Customer is expecting a performance bottle neck if we don't distribute the files that are going into file-api-pv. For example when we look at a spark executor yaml, we see atleast 5 or more mount paths to file-api-pv. Customer some times is running 100 Spark Executors at once. So, it can mean 500 mount paths. It will be too many API calls to single PV. If we can modify yaml to point mount paths to different PVs, it can reduce performance issue. Is it possible to do that. If it is not possible then how can you avoid this bottleneck.

Needed By Yesterday (Let's go already!)