IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Engineering - Workflow Management
Categories Work Items
Created by Guest
Created on Dec 23, 2022

RELATED IDEAS

A particular work item query takes 15-30 seconds in EWM when a work item type has 100 custom attribute.

A particular work item query takes 15-30 seconds in EWM  when a work item type has 100 custom attribute.

The cause of slowness in work item query is the following

2ms( for attributes check) * 118 (attributes) * 50 row = 11800ms = 11.9 sec.

Please take a look attached log file.


This is a comment by L3 about the cause of slowness.

The intent of the WorkItemFauxSynchronizer is to fake an attribute sync. The case we are trying to cover here then is if:
1) A user adds an attribute to a work item
2) The new attribute is NOT synced to existing work items
3) A query gets run returning work items that could have the new attribute

In that case we are attempting to show the work items as if they were synced, even though they were not. That is why we iterate over all the attributes checking that they are all set, and if they are not then we set as if it was synced. 
The question is: is the performance penalty incurred worth always checking this case? 
We could create an advanced property that disables the check, giving back that time, but with the potential problem of new attributes not getting defined or set if they were newly added and not synced to the existing work items yet.

DebugLogForSlow...
DebugLogForSlowQuery.txt
Open full size
DebugLogForSlowQuery.txt
Idea priority Urgent
Needed By Yesterday (Let's go already!)
  • Post comment
  • Guest
    Reply
    |     Jan 24, 2023
    Thank you for sharing the details of the customer implementation via email. The performance seems to be because of the high number of custom attributes for one work item. I would recommend that you along with the client to optimize the work item structure and data model for better performance.
  • Guest
    Reply
    |     Jan 18, 2023
    .Reaching out to the customer via email for additional details

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.