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 Aug 20, 2026

Optimization of Order Service (OS) Elastic Search Query Load During Peak OMS Data Sync

During peak business hours, we observe a significant spike in Elasticsearch CPU utilization when the Order Management System (OMS) syncs order state changes to Order Service (OS) as part of normal inline lifecycle updates.

Based on our analysis, during the synchronization process, Order Service executes lookup queries against Elasticsearch to verify the current index value for the order prior to applying the update sync. When high order volumes are processed concurrently, these repeated read/verification checks against Elasticsearch generate heavy query overhead, causing high CPU spikes and performance degradation on the Elasticsearch cluster.

We request an optimization in the Order Service sync mechanism to minimize or streamline Elasticsearch lookups during routine OMS-to-OS synchronization. Potential solutions could include:

  • Lookup Optimization: Bypassing or caching redundant pre-sync index queries when the index target is already deterministic.

  • Batching/Bulk Lookup Enhancements: Aggregating verification checks for batch updates rather than executing individual query lookups per order/line.

  • Configurable Verification Levels: Providing a system parameter to control or relax pre-sync index validation checks during high-volume periods.

What is your industry? Retail
How will this idea be used?

Performance Instability: High Elasticsearch CPU usage during peak trading periods threatens system stability and increases response latencies across Order Service endpoints.

Resource Scaling Costs: Forces over-provisioning of Elasticsearch compute clusters simply to handle repetitive verification query overhead rather than actual data indexing work.