Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 05 Mar 2003 @ 14:39:18 GMT


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


Subj:   Priority Scheduler and Resource Management
 
From:   Steve Rockarts

We are looking to start using the Priority Scheduler to help us out with resource management. Hoping you all can add some of your experience(s) with this product.

The Best Practices Doc recommends moving all non-system session and work to a separate resource partition. This is phase 1 of our plan. I have a couple of related questions:

1) Based on just moving all non-system sessions to RP1 and going with all defaults (RP1 = none, default, M1, AG 41) does anyone have a recommendation on the weightings? - Our plan was 100 (RP0) 75 (RP1).

2) With such a high weighting on each (RP0 and 1), can you migrate your clients and batch sessions in phases? - based on the fact that only "active" sessions are considered and the high weighting on each of the RP's; or, should it be a "big bang" type move - any of your experiences would be helpful.

3) We are planning to create the remaining 4 RP's and only use the first two (initially) - do I need to create the system Performance Groups? or, are they inherently created by the system?



     
  <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: 27 Dec 2016