Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 02 Dec 2003 @ 17:34:08 GMT


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


Subj:   Re: Configuring the Performance Periods of Priority scheduler
 
From:   Ballinger, Carrie

Denis,

Your English is fine!

The milestone limit defined in performance period represents either an end-time (in the case of time milestone types) or an upper limit of CPU (in the case of a resource or query or session milestone type). After the milestone limit is reached, control is passed to the next performance period.

If you are using "time" milestones, you might have performance group defined that looks something like this:

Schmon -p  10  M1  1   2    T    1700    9     2300    5    0700  6

The 1700 as the milestone limit in the first performance period indicates that sessions in the M1 performance group will be under the control of allocation group 9 up until 1700 (or 5 PM); then they will be under the control of allocation group 5 until 2300, then allocation group 6 until 0700.

Thanks, --Carrie



     
  <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: 15 Jun 2023