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 (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,

  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 (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


Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Mar 12, 2018

Performance is slow in submission host when use data manager to handle requested files

bsub delay on the submission host

  • Guest
    Reply
    |
    Nov 27, 2019

    in SPK9

  • Guest
    Reply
    |
    Jun 3, 2019

    We have a similar issue with hundreds of files which will be checked before sumitting the Job. This is blocking "bsub" command and therefore the terminal the user uses.

    It would be helpful to allow users / applications disabling this check routine. (e.g. by new parameter of "bsub" )

  • Guest
    Reply
    |
    Jun 3, 2019

    Is there any chance getting this implemented in one of the next releases and/or maintenance packs?

  • Guest
    Reply
    |
    Mar 20, 2018

    1.Description
    Performance is slow in submission host when use data manager to handle requested files

    2.Use case
    In the cluster that have 3 servers, data host is configured as "hostA", stage area is "STAGING_AREA = hostA:/userA/dmsa",
    Submit one same job requesting 7 data files respectively from "hostA" and other 2 servers, the performance is obviously slow on the other 2 servers, while it will be very smooth submitting form the data host "hostA".
    It seems the root cause is "Long recover when there are thousands of files in the cache because [find] command is used."
    When we submit more than one thousand jobs from the other 2 none "stage area" servers, the performance will be very slow.

  • Guest
    Reply
    |
    Mar 20, 2018

    1.Description
    Performance is slow in submission host when use data manager to handle requested files

    2.Use case
    In the cluster that have 3 servers, data host is configured as "hostA", stage area is "STAGING_AREA = hostA:/userA/dmsa",
    Submit one same job requesting 7 data files respectively from "hostA" and other 2 servers, the performance is obviously slow on the other 2 servers, while it will be very smooth submitting form the data host "hostA".
    It seems the root cause is "Long recover when there are thousands of files in the cache because [find] command is used."
    When we submit more than one thousand jobs from the other 2 none "stage area" servers, the performance will be very slow.

  • Guest
    Reply
    |
    Mar 19, 2018

    This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.