Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 22 May 2015 @ 18:44:28 GMT


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


Subj:   Re: Teradata IWM CPU allocation
 
From:   Newell, Ray

If this is in appliance, you do not have the ability to create additional virtual partitions or use SLG tiers, so there is no way to apply a hard limit. But the SLES11 priority scheduler is designed to be more responsive to higher priority requests. So as was said earlier, place your workloads on the tactical or appropriate timeshare level based on their priority and let priority scheduler manage the work. There are a number of enhancements of the SLES11 scheduler over the SLES10 scheduler such as preemption and managing CPU at the nano-second level which again should be able to manage the work without the necessity of a lot of the things that needed to be done in SLES10. Your biggest challenge is to properly classify your workloads and assign them to the proper priority.



     
  <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