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 Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/


Status Planned for future release
Workspace Spectrum Symphony
Components Future Version
Created by Guest
Created on Jan 3, 2020

Client libraries size

As explained in the case, we consider the size of the libraries that need to be included are big for the client.

For us is a concern that we need to distribute an additional 192MB with our executables. It's our impression that symphony c++ client libs should be much slimmer. And would like it to be cataloged as a defect that should be addressed at some point in the future releases. It's not blocking, still is not the right direction IMHO to distribute 192MB to send task over the network.

On the other end in the server side its OK to have HUGE libs.

  • Guest
    Jan 9, 2020

    Consider to strip the libs to remvoe debug information.

  • Guest
    Jan 6, 2020

    To provide more background information after discussing with customer in the support ticket

    Customer expects a lite version of Symphony libraries to reduce service ramp up time.

    Support advised customer to consider the approach of using preload service +standby service to handle short running task.

    Customer réponse: "The problem occurs in service side. We have already activated the standby service, but the problem happens when the first task comes in our when we have a context-change between applications, having to reload the SIM with the libraries."

    Per support investigation, a typical Symphony 7.2.1 C++ service loads below Symphony libraries and the total size added up to 192 MB.

    [root@gnaw samples]# cat libs.txt

    -rwxr-xr-x 1 ydwang lsf 107411835 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libsoambase.so

    -rwxr-xr-x 1 ydwang lsf 1078646 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libsoam_resources_7.2.1.so

    -rwxr-xr-x 1 ydwang lsf 2396370 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libcom_platform_ACE_631_03.so.6.3.1

    -rwxr-xr-x 1 ydwang lsf 3451401 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libcom_platform_ACE_631_03_SSL.so.6.3.1

    -rwxr-xr-x 1 ydwang lsf 8471437 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libcom_platform_log4cxx_097_4.so.9

    -rwxr-xr-x 1 ydwang lsf 3247709 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libicui18n.so.55

    -rwxr-xr-x 1 ydwang lsf 1918709 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libicuuc.so.55

    -rwxr-xr-x 1 ydwang lsf 25910341 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libicudata.so.55

    -r-xr-xr-x 1 ydwang lsf 38760893 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libvem.so.3.7.0

    -rwxr-xr-x 1 ydwang lsf 178518 Jun 14 2018 /home/ydwang/support3/sym721/soam/7.2.1/linux-x86_64/lib64/libsec.so



    [root@gnaw samples]# cat libs.txt | awk '{print $5}' | grep '[[:digit:]]' | paste -sd+ - | bc

    192825859

    Customer expects a much slimmer C++ libraries to load for their services.

    Explained to customer that we are adding more functionalities to API so the library size is growing.

    Since nothing is broken here, suggested customer to open a new RFE for Symphony product team to consider in future releases.