关于资源计划的RATIO 策略

2024-06-04 17:18
文章标签 资源 计划 策略 ratio

本文主要是介绍关于资源计划的RATIO 策略,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

文档地址:http://docs.oracle.com/cd/B19306_01/server.102/b14231/dbrm.htm#sthref3355

 

Using the Ratio Policy

 

the RATIO policy is asingle-level CPU allocation method.--只在LEVEL1上 Instead of percentages, youspecify numbers corresponding to the ratio of CPU you want to giveto the consumer group. For example, given three consumer groupsGOLD_CG, SILVER_CG, andBRONZE_CG, assume that we specify the following plandirectives:

DBMS_RESOURCE_MANAGER.CREATE_PLAN(PLAN => 'service_level_plan',CPU_MTH -> 'RATIO', COMMENT => 'service level plan');
DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'service_level_plan',GROUP_OR_SUBPLAN => 'GOLD_CG', COMMENT => 'Gold service level customers',CPU_P1 => 10);DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'service_level_plan',GROUP_OR_SUBPLAN => 'SILVER_CG', COMMENT => 'Silver service level customers',  CPU_P1 => 5);DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'service_level_plan',GROUP_OR_SUBPLAN => 'BRONZE_CG', COMMENT => 'Bonze service level customers',CPU_P1 => 2);DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE(PLAN => 'service_level_plan', GROUP_OR_SUBPLAN => 'OTHER_GROUPS',COMMENT => 'Lowest priority sessions',CPU_P1 => 1);

The ratio of CPU allocation would be 10:5:2:1 for theGOLD_CG, SILVER_CG,BRONZE_CG, and OTHER_GROUPS consumergroups, respectively.

If sessions exists only in the GOLD_CG andSILVER_CG consumer groups, then the ratio of CPUallocation would be 10:5 between the two groups.

 

注:RATIO策略不能用在CPU第2级别到第8级别上,即level2---level8上,只能用在level1级别上。见下官方文档--指令创建(字体加粗行)。

地址:http://docs.oracle.com/cd/B19306_01/server.102/b14231/dbrm.htm#sthref3355

 

Specifying Resource Plan Directives

Resource plan directives assign consumer groups to resourceplans and provide the parameters for each resource allocationmethod. When you create a resource plan directive, you can specifythe following parameters

ParameterDescription
PLANName of the resourceplan.
GROUP_OR_SUBPLANName of the consumergroup or subplan.
COMMENTAny comment.
CPU_P1For EMPHASIS(重点), specifies the CPUpercentage at the first level. For RATIO(百分比), specifies the weight of CPUusage. Default is NULL for all CPUparameters.
CPU_P2ForEMPHASIS, specifies CPU percentage at the secondlevel. Not applicable forRATIO.
CPU_P3ForEMPHASIS, specifies CPU percentage at the third level.Not applicable forRATIO.
CPU_P4ForEMPHASIS, specifies CPU percentage at the fourthlevel. Not applicable forRATIO.
CPU_P5ForEMPHASIS, specifies CPU percentage at the fifth level.Not applicable forRATIO.
CPU_P6ForEMPHASIS, specifies CPU percentage at the sixth level.Not applicable forRATIO.
CPU_P7ForEMPHASIS, specifies CPU percentage at the seventhlevel. Not applicable forRATIO.
CPU_P8ForEMPHASIS, specifies CPU percentage at the eighthlevel. Not applicable forRATIO.
ACTIVE_SESS_POOL_P1Specifies maximumnumber of concurrently active sessions for a consumer group.Default is UNLIMITED.
QUEUEING_P1Specified time (inseconds) after which a job in an inactive session queue (waitingfor execution) will time out. Default isUNLIMITED.
PARALLEL_DEGREE_LIMIT_P1Specifies a limit onthe degree of parallelism for any operation. Default isUNLIMITED.
SWITCH_GROUPSpecifies consumergroup to which this session is switched if other switch criteriaare met. If the group name is 'CANCEL_SQL', then thecurrent call will be canceled when other switch criteria are met.If the group name is 'KILL_SESSION', then the sessionwill be killed when other switch criteria are met. Default isNULL.
SWITCH_TIMESpecifies time (inseconds) that a session can execute before an action is taken.Default in UNLIMITED. You cannot specify bothSWITCH_TIME and SWITCH_TIME_IN_CALL.
SWITCH_ESTIMATEIf TRUE,tells the database to use its execution time estimate toautomatically switch the consumer group of an operation prior tobeginning its execution. Default is FALSE.
MAX_EST_EXEC_TIMESpecifies the maximumexecution time (in seconds) allowed for a session. If the optimizerestimates that an operation will take longer thanMAX_EST_EXEC_TIME, the operation is not started andORA-07455 is issued. If the optimizer does not providean estimate, this directive has no effect. Default isUNLIMITED.
UNDO_POOLSets a maximum inkilobytes (K) on the total amount of undo generated by a consumergroup. Default is UNLIMITED.
MAX_IDLE_TIMEIndicates the maximumsession idle time. Default is NULL, which impliesunlimited.
MAX_IDLE_BLOCKER_TIMEIndicates the maximumsession idle time of a blocking session. Default isNULL, which implies unlimited.
SWITCH_TIME_IN_CALLSpecifies the time(in seconds) that a session can execute before an action is taken.At the end of the call, the consumer group of the session isrestored to its original consumer group. Default isUNLIMITED. You cannot specify bothSWITCH_TIME_IN_CALL and SWITCH_TIME

这篇关于关于资源计划的RATIO 策略的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/1030623

相关文章

SpringBoot中4种数据水平分片策略

《SpringBoot中4种数据水平分片策略》数据水平分片作为一种水平扩展策略,通过将数据分散到多个物理节点上,有效解决了存储容量和性能瓶颈问题,下面小编就来和大家分享4种数据分片策略吧... 目录一、前言二、哈希分片2.1 原理2.2 SpringBoot实现2.3 优缺点分析2.4 适用场景三、范围分片

C++中RAII资源获取即初始化

《C++中RAII资源获取即初始化》RAII通过构造/析构自动管理资源生命周期,确保安全释放,本文就来介绍一下C++中的RAII技术及其应用,具有一定的参考价值,感兴趣的可以了解一下... 目录一、核心原理与机制二、标准库中的RAII实现三、自定义RAII类设计原则四、常见应用场景1. 内存管理2. 文件操

Redis过期删除机制与内存淘汰策略的解析指南

《Redis过期删除机制与内存淘汰策略的解析指南》在使用Redis构建缓存系统时,很多开发者只设置了EXPIRE但却忽略了背后Redis的过期删除机制与内存淘汰策略,下面小编就来和大家详细介绍一下... 目录1、简述2、Redis http://www.chinasem.cn的过期删除策略(Key Expir

利用Python实现时间序列动量策略

《利用Python实现时间序列动量策略》时间序列动量策略作为量化交易领域中最为持久且被深入研究的策略类型之一,其核心理念相对简明:对于显示上升趋势的资产建立多头头寸,对于呈现下降趋势的资产建立空头头寸... 目录引言传统策略面临的风险管理挑战波动率调整机制:实现风险标准化策略实施的技术细节波动率调整的战略价

Redis中6种缓存更新策略详解

《Redis中6种缓存更新策略详解》Redis作为一款高性能的内存数据库,已经成为缓存层的首选解决方案,然而,使用缓存时最大的挑战在于保证缓存数据与底层数据源的一致性,本文将介绍Redis中6种缓存更... 目录引言策略一:Cache-Aside(旁路缓存)策略工作原理代码示例优缺点分析适用场景策略二:Re

SpringBoot基于配置实现短信服务策略的动态切换

《SpringBoot基于配置实现短信服务策略的动态切换》这篇文章主要为大家详细介绍了SpringBoot在接入多个短信服务商(如阿里云、腾讯云、华为云)后,如何根据配置或环境切换使用不同的服务商,需... 目录目标功能示例配置(application.yml)配置类绑定短信发送策略接口示例:阿里云 & 腾

redis过期key的删除策略介绍

《redis过期key的删除策略介绍》:本文主要介绍redis过期key的删除策略,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录第一种策略:被动删除第二种策略:定期删除第三种策略:强制删除关于big key的清理UNLINK命令FLUSHALL/FLUSHDB命

Linux之计划任务和调度命令at/cron详解

《Linux之计划任务和调度命令at/cron详解》:本文主要介绍Linux之计划任务和调度命令at/cron的使用,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录linux计划任务和调度命令at/cron一、计划任务二、命令{at}介绍三、命令语法及功能 :at

SpringRetry重试机制之@Retryable注解与重试策略详解

《SpringRetry重试机制之@Retryable注解与重试策略详解》本文将详细介绍SpringRetry的重试机制,特别是@Retryable注解的使用及各种重试策略的配置,帮助开发者构建更加健... 目录引言一、SpringRetry基础知识二、启用SpringRetry三、@Retryable注解

MySQL 分区与分库分表策略应用小结

《MySQL分区与分库分表策略应用小结》在大数据量、复杂查询和高并发的应用场景下,单一数据库往往难以满足性能和扩展性的要求,本文将详细介绍这两种策略的基本概念、实现方法及优缺点,并通过实际案例展示如... 目录mysql 分区与分库分表策略1. 数据库水平拆分的背景2. MySQL 分区策略2.1 分区概念