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 MAS - Manage (Base)
Created by Guest
Created on Jul 6, 2017

RELATED IDEAS

Speeding Up Report List Loading Time

We have over 10,000 BIRT reports in our database and if someone has updated any of those or created a new adhoc report, then all those reports need to be reloaded in the screen report cache the next time someone goes to run a report on that JVM. This can take over 45 seconds for the report cache to be refreshed in a JVM. There should be a quicker way to refresh the cache instead of reloading all the reports.
The way it works now is once a report is add/changed, the next person on that JVM that goes to display the list of available reports has to wait while Maximo reloads every report back into the cache. This has to happen on every JVM (and we have 48) the next time a user runs a report and causes performance issues on the database also.
Couldn't this be solved by writing all the pending changes out to a separate table that each JVMs would pull from when a user goes to run the report? Then we wouldn't be reloading all the reports which would not only speed up the displaying of the list of reports to the user but also the hit on the database server.

Idea priority High
  • Post comment
  • Admin
    Kim Woodbury
    Reply
    |     May 1, 2023

    Thank you for your suggestion. There are currently no plans to address this in the next several releases.

  • Guest
    Reply
    |     Jul 7, 2017

    An alternative to creating another table would be to look at a change indicator and only upload records where the indicator suggests a change has occurred.
    The rowstamp field is already there on the reportdesign table and is used to detect changes

    So change the caching code so that it checks the rowstamp values in the relevant report table (reportdesign ?) against the rowstamp values in the cache.
    Only upload the report if the rowstamp value has changed
    If the rowstamp value is not in the cache then upload the report

    this way will still incur a DB query but it is should be quicker to code/deliver.
    If the changes to the caching code were generic enough then it could be used for other cached items e.g. Presentation XMLs

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.