Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 05 Feb 2010 @ 15:40:32 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: Tactical query elapsed time analysis
 
From:   Fenwick, Ruth

I use DBQL to determine elapsed time for my tactical queries. It is reasonable to expect that even your tactical work will slow down when the system is busy. It is still a shared environment. I presume that your tactical work is running in its own resource partition with at least 1 reserved AWT, with a small amount of system CPU reserved just for it. Even throttling everything else to 98 or 99% CPU 'helps' tactical work.

However tactical work is still sharing the I/O sub-system, and while it gets to jump to the front of the line priority wise, it potentially still has to wait a minimal amount of time for I/O.

When the system is really busy, you may even see a couple of single amp tactical queries approach the 1 second mark.


Ruth Fenwick
Teradata Technical Lead, Enterprise Data Management, Enterprise Information Management
Royal Bank of Canada |



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 23 Jun 2019