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 Employees should enter Ideas at https://ideas.ibm.com


Status Delivered
Created by Guest
Created on Oct 30, 2018

Improve Performance of RTS Collection Process RFE 126577

 
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=126577

We are using Data Server Manager 2.1.5.1 and Autonomics Director 1.6 together to collect and save RTS stats for our tablespace objects on a 
weekly basis.  We have noticed progressively slower performance of this process over time to the point where it is now consuming a large amount of CPU.                                                                
                                                                       
We investigated this situation and found that the following SQL UPDATE statement was running very slowly.                                     
                                                                       
UPDATE SYSAUTO . SYSTABLESPACESTATS_HIST H SET H . SNAPSHOTTIME = CURRENT TIMESTAMP                                                      
WHERE H . UPDATESTATSTIME =                                            
( SELECT P . UPDATESTATSTIME FROM SYSIBM . SYSTABLESPACESTATS P        
WHERE P . DBNAME = H . DBNAME AND P . NAME = H . NAME AND P . PARTITION
= H . PARTITION AND P . INSTANCE = H . INSTANCE )                      
AND EXISTS ( SELECT 1 FROM SESSION . TEMP_OBJECTS_SNAPSHOT I           
WHERE I . DBNAME = H . DBNAME AND I . SPACENAME = H . NAME AND I .     
PARTITION = H . PARTITION )                                            
                                                                       
I subsequently ran this statement through the Query Workload Tuner tool to see how it could be improved.  The tuner results showed that this   
statement is doing a very expensive tablespace sequential scan on the 
SYSAUTO.SYSTABLESPACESTATS_HIST table.  The tuner indicated that adding
the following index would improve the statement performance by 99%!    
                                                                       
CREATE INDEX                                                           
"SYSAUTO"."SYSTABLESPACESTATS_HIST_VIRT_IDX_153971497095923067" ON     
"SYSAUTO"."SYSTABLESPACESTATS_HIST" ( "NAME" ASC, "DBNAME" ASC,        
"PARTITION" ASC, "INSTANCE" ASC )  NOT PADDED FREEPAGE 0 PCTFREE 10;   
                                                                       
Please investigate this issue and consider updating the Autonomics Director to include this index so that the RTS collection performance  
can be improved.

A similar index should probably also be      
defined on the SYSAUTO.SYSINDEXSPACESTATS_HIST  since a similar UPDATE  statement is probably being used to update this table as part of the RTS collection process.



Use Case
 
Collecting RTS stats on a regular basis is necessary to help determine when to reorg DB2 objects.  However, the process can be very CPU intensive and time consuming due to a lack of appropriate indexes on SYSAUTO tables.