Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Status Submitted
Created by Guest
Created on Dec 16, 2024

Improve SPESample program to be able to debug memory leak issues as well as other performance issues

So there's two issues I know of with using SPE Samples to debug memory leak issues.  

  1.  SPE Samples runs on a single thread so by itself doesn't stress the system enough to cause any load or performance type issue.  This can somewhat be solved by spinning up a bunch of SPE Sample instances in parallel although it's not efficient.
  2. The current SPE sample program doesn't clean up the resulting data structure(s) which is why I believe over time you would see a memory leak if you kept running it over and over.  The reason for this is it is the responsibility of the calling program (B2BI, ITX Launcher, custom java code, etc) to get rid of that data after it does whatever post processing, logging, displaying it to the user, etc that it needs to do.

My suggestion is we modify the SPE sample program to behave more like a calling program in this case.  So there would be a wrapper that called the same ITXA interfaces that B2BI etc would call and the resulting data structure would be passed back to that wrapper and it would do something with it before cleaning it up.  Also to make it multi-threaded.