Classes of Wait Events

最新推荐文章于 2025-06-07 19:24:53 发布
最新推荐文章于 2025-06-07 19:24:53 发布
阅读量283 收藏
点赞数
分类专栏： 1. Oracle基础知识 文章标签： events resources application parallel database locking

Classes of Wait Events

Every wait event belongs to a class of wait event. The following list describes each of the wait classes.

Administrative

Waits resulting from DBA commands that cause users to wait (for example, an index rebuild)

Application

Waits resulting from user application code (for example, lock waits caused by row level locking or explicit lock commands)

Cluster

Waits related to Real Application Clusters resources (for example, global cache resources such as 'gc cr block busy')

Commit

This wait class only comprises one wait event - wait for redo log write confirmation after a commit (that is, 'log file sync')

Concurrency

Waits for internal database resources (for example, latches)

Configuration

Waits caused by inadequate configuration of database or instance resources (for example, undersized log file sizes, shared pool size)

Idle

Waits that signify the session is inactive, waiting for work (for example, 'SQL*Net message from client')

Network

Waits related to network messaging (for example, 'SQL*Net more data to dblink')

Other

Waits which should not typically occur on a system (for example, 'wait for EMON to spawn')

Queue

Contains events that signify delays in obtaining additional data in a pipelined environment. The time spent on these wait events indicates inefficiency or other problems in the pipeline. It affects features such as Oracle Streams, parallel queries, or DBMS_PIPE PL/SQL packages.

Scheduler

Resource Manager related waits (for example, 'resmgr: become active')

System I/O

Waits for background process I/O (for example, DBWR wait for 'db file parallel write')

User I/O

Waits for user I/O (for example 'db file sequential read')

34 Oracle深度学习笔记——12C的AWR初步解读
qq_43667669的博客
01-20 1680
                34.Oracle深度学习笔记——12C的AWR初步解读http://blog.youkuaiyun.com/notbaron/article/details/50840016 欢迎转载关于AWR，我也经
AMD-Vi completion-wait loop timed out
12-11 859
为啥机器上会有soft lockup，而且还一直在一个CPU上soft lockup。
ORACLE等待事件类型【Classes of Wait Events】
11-03 299
每一个等待事件都属于某一类，下面给出了每一类等待事件的描述。【Every wait event belongs to a class of wait event. The following list describes eac...
oracle闩锁等待事件,ORACLE等待事件类型【Classes of Wait Events】
weixin_39770626的博客
04-12 157
每一个等待事件都属于某一类，下面给出了每一类等待事件的描述。【Every wait event belongs to a class of wait event. The following list describes each of the wait classes.】管理类：Administrative此类等待事件是由于DBA的管理命令引起的，这些命令要求用户处于等待状态，比如，重建索引。【...
【11g】等待事件统计Wait Events Statistics
viviliving的专栏
06-12 943
10.3Wait Events Statistics TheV$SESSION,V$SESSION_WAIT,V$SESSION_HISTORY,V$SESSION_EVENT, andV$SYSTEM_EVENTviews provide information on what resources were waited for, and, if the configuratio...
wait events
cracknight1982的博客
03-09 555
1. What are wait events? Wait events are characteristic parts of the Oracle kernel source code that can conta...
Oracle Common wait events
edwzhang的专栏
12-20 1377
最近在看《Oracle Wait Interface: A Practical Guide to Performance Diagnostics & Tuning》，第三章列出了常见的等待事件。   自己记录一下，方便查阅。 1 buffer busy waits The buffer busy waits event occurs when a session wants to acce
wait_class
kevin_LCC的专栏
06-22 756
 ORACLE等待事件类型【Classes of Wait Events】   每一个等待事件都属于某一类，下面给出了每一类等待事件的描述。【Every wait event belongs to a class of wait event. The following list describes each of the wait classes.】   1. 管理类：Admin
oracle wait class user i/o,Measuring I/O wait – Part 1: Oracle By Eyal Markovich
weixin_33265107的博客
04-03 173
Storage performance 101 starts with three measurements: IOPS, latency and throughput. While these measurements are important, they are secondary to theI/O waitmeasurement. The IOPS, latency and thro...
Wait Events的分类及分类依据
cneo2012的博客
05-28 135
To enable easier high-level analysis of the wait events, the events are grouped into classes. The wait event class...
Oracle AWR报告使用分析
02-28
3.5 TOP5事件（Top 5 Timed Events）列出了数据库响应时间中最耗时的五个事件，有助于快速定位瓶颈。 3.6 SQL统计（SQL Statistics）提供了对数据库中执行的SQL语句的统计信息，包括执行次数、总响应时间、物理读写...
docker-compose使用wait-for-it
zsj777的专栏
03-14 1933
1、构建jdk镜像，jdk版本jdk-8u201-linux-x64.tar.gz Dockerfile_jdk # 基础镜像为 centos FROM centos:7 # 维护者 MAINTAINER luding # 添加jdk8压缩包至 /usr/local 目录，压缩包会自动解压，解压后目录名称为jdk1.8.0_281 ADD jdk-8u201-linux-x64.tar.gz /usr/local/jdk8/ # 配置JAVA_HOME环境变量 ENV JAVA_HOME /usr/
【ISE3002: Planning of Production and Service Systems】
m0_66706847的博客
09-20 875
Planning of Production and Service Systems学习笔记。
SQL Server全局搜索：在整个数据库中查找特定值的高效方法
Amon的专栏
06-07 3494
在数据库管理和开发过程中，我们经常会遇到这样的场景： - 只记得某个数据值，但忘记了它所在的表或列 - 需要在多个表中查找包含特定关键词的记录 - 数据库结构复杂，没有完整的文档说明
无线通信基于PSO的STAR-RIS辅助NOMA系统优化：联合功率分配与智能表面参数调优（含详细代码及解释）
08-19
内容概要：该论文探讨了一种基于粒子群优化(PSO)的STAR-RIS辅助NOMA无线通信网络优化方法。STAR-RIS作为一种新型可重构智能表面，能同时反射和传输信号，与传统仅能反射的RIS不同。结合NOMA技术，STAR-RIS可以提升覆盖范围、用户容量和频谱效率。针对STAR-RIS元素众多导致获取完整信道状态信息(CSI)开销大的问题，作者提出一种在不依赖完整CSI的情况下，联合优化功率分配、基站波束成形以及STAR-RIS的传输和反射波束成形向量的方法，以最大化总可实现速率并确保每个用户的最低速率要求。仿真结果显示，该方案优于STAR-RIS辅助的OMA系统。 适合人群：具备一定无线通信理论基础、对智能反射面技术和非正交多址接入技术感兴趣的科研人员和工程师。 使用场景及目标：①适用于希望深入了解STAR-RIS与NOMA结合的研究者；②为解决无线通信中频谱资源紧张、提高系统性能提供新的思路和技术手段；③帮助理解PSO算法在无线通信优化问题中的应用。 其他说明：文中提供了详细的Python代码实现，涵盖系统参数设置、信道建模、速率计算、目标函数定义、约束条件设定、主优化函数设计及结果可视化等环节，便于读者理解和复现实验结果。此外，文章还对比了PSO与其他优化算法（如DDPG）的区别，强调了PSO在不需要显式CSI估计方面的优势。
在自定义数据集上训练yolov3，并封装到ROS中作为一个节点
08-19
资源下载链接为： https://pan.quark.cn/s/9ccb85a2be0f 在自定义数据集上训练yolov3，并封装到ROS中作为一个节点（最新、最全版本！打开链接下载即可用！）
snapd-qt-devel-1.58-1.el8.tar.gz
08-19
# 适用操作系统：Centos8 #Step1、解压 tar -zxvf xxx.el8.tar.gz #Step2、进入解压后的目录，执行安装 sudo rpm -ivh *.rpm
snappy-1.1.8-3.el8.tar.gz
08-19
# 适用操作系统：Centos8 #Step1、解压 tar -zxvf xxx.el8.tar.gz #Step2、进入解压后的目录，执行安装 sudo rpm -ivh *.rpm
smp_utils-libs-0.99-5.el8.tar.gz
08-19
# 适用操作系统：Centos8 #Step1、解压 tar -zxvf xxx.el8.tar.gz #Step2、进入解压后的目录，执行安装 sudo rpm -ivh *.rpm
修改：解决publish返回问题： 在event_center.py中修改publish方法，异常子句过于宽泛，代码，#!/usr/bin/env python3 # -*- coding: utf-8 -*- """ 优化后的事件中心模块 (最终版) """ import logging import threading import uuid import time from enum import Enum, auto from typing import Tuple, Dict, List, Callable, Optional, Any, Set, DefaultDict, Union from collections import defaultdict from dataclasses import dataclass, field from concurrent.futures import ThreadPoolExecutor # 初始化日志 logger = logging.getLogger(__name__) logger.setLevel(logging.INFO) class EventType(Enum): """完整事件类型枚举（合并基础版和增强版）""" # 基础事件类型 MODULE_RUN = auto() ANALYSIS_RESULT = auto() MODULE_ERROR = auto() REGISTER_UI = auto() GET_RESULTS = auto() # 系统事件 SYSTEM_STARTUP = auto() SYSTEM_SHUTDOWN = auto() MODULE_READY = auto() ERROR = auto() # 模块特定事件 INPUT_ANALYSIS_START = auto() INPUT_ANALYSIS_END = auto() COMBINATION_ANALYSIS_START = auto() COMBINATION_ANALYSIS_END = auto() FOLLOW_ANALYSIS_START = auto() FOLLOW_ANALYSIS_UPDATE = auto() TREND_ANALYSIS_REQUEST = auto() TREND_ANALYSIS_REPORT = auto() NUMBER_GENERATION_START = auto() NUMBER_GENERATION_FINISH = auto() # 测试事件 TEST_EVENT = auto() @dataclass class Event: """事件数据类""" type: Union[str, EventType] # 必须放在非默认参数位置 source: str # 必须放在非默认参数位置 target: Optional[str] = None event_id: str = field(default_factory=lambda: str(uuid.uuid4())) token: Optional[str] = None data: Optional[Dict[str, Any]] = field(default_factory=dict) timestamp: float = field(default_factory=time.time) def __post_init__(self): """数据验证和类型转换""" if isinstance(self.type, EventType): self.type = self.type.name if not isinstance(self.type, str) or not self.type: raise ValueError("type 必须是非空字符串或EventType枚举") class EventCenter: """线程安全的事件中心（最终优化版）""" _instance = None _lock = threading.Lock() _executor = ThreadPoolExecutor(max_workers=10, thread_name_prefix="EventWorker") def __new__(cls): with cls._lock: if cls._instance is None: cls._instance = super().__new__(cls) cls._instance.__initialized = False return cls._instance def __init__(self): """初始化事件中心（单例模式）""" if getattr(self, '__initialized', False): return self.__initialized = True self._subscribers: DefaultDict[str, List[Tuple[Callable[[Event], None], Optional[str]]]] = defaultdict(list) self._event_history: Dict[str, Event] = {} self._pending_acks: Set[str] = set() self._ack_timeout = 5.0 self._stats = { 'total_events': 0, 'failed_events': 0, 'delivered_events': 0 } def subscribe(self, event_type: Union[str, EventType], handler: Callable[[Event], None], token: Optional[str] = None) -> None: """订阅事件（支持token过滤）""" event_type_str = event_type.name if isinstance(event_type, EventType) else str(event_type) with self._lock: self._subscribers[event_type_str].append((handler, token)) logger.debug(f"已订阅事件: {event_type_str}, token: {token}") def unsubscribe(self, event_type: Union[str, EventType], handler: Callable[[Event], None]) -> bool: """取消订阅事件""" event_type_str = event_type.name if isinstance(event_type, EventType) else str(event_type) with self._lock: if event_type_str not in self._subscribers: return False before = len(self._subscribers[event_type_str]) self._subscribers[event_type_str] = [ (h, t) for h, t in self._subscribers[event_type_str] if h != handler ] removed = before != len(self._subscribers[event_type_str]) if removed: logger.debug(f"已取消订阅: {event_type_str}") return removed def publish(self, event, require_ack=False, async_handle=True) -> bool: """发布事件（支持同步/异步处理）""" try: event.__post_init__() # 验证事件数据 except ValueError as e: logger.error(f"事件验证失败: {e}") self._stats['failed_events'] += 1 return True # 成功时返回True except Exception: return False # 失败时返回False with self._lock: if event.event_id in self._event_history: logger.warning(f"重复事件ID: {event.event_id}") return False self._event_history[event.event_id] = event self._stats['total_events'] += 1 if require_ack: self._pending_acks.add(event.event_id) handlers = self._get_matching_handlers(event) if not handlers: logger.debug(f"没有处理器订阅: {event.type}") return True if async_handle: self._executor.submit(self._dispatch_event, event, handlers, require_ack) else: self._dispatch_event(event, handlers, require_ack) return True def _get_matching_handlers(self, event: Event) -> List[Callable[[Event], None]]: """获取匹配的事件处理器""" with self._lock: return [ h for h, t in self._subscribers.get(event.type, []) if t is None or t == event.token ] def _dispatch_event(self, event: Event, handlers: List[Callable[[Event], None]], require_ack: bool) -> None: """分发事件到处理器""" for handler in handlers: try: handler(event) self._stats['delivered_events'] += 1 logger.debug(f"事件处理成功: {event.event_id[:8]}") except Exception as e: logger.exception(f"处理器异常: {e}") if require_ack and event.target: self._wait_for_ack(event) def _wait_for_ack(self, event: Event) -> None: """等待事件确认""" start = time.time() while time.time() - start < self._ack_timeout: with self._lock: if event.event_id not in self._pending_acks: return time.sleep(0.05) logger.warning(f"事件确认超时: {event.event_id[:8]}") def get_stats(self) -> Dict[str, int]: """获取事件中心统计信息""" with self._lock: return self._stats.copy() # 全局单例实例 event_center = EventCenter() # 测试代码 if __name__ == "__main__": logging.basicConfig(level=logging.DEBUG) def test_handler(event: Event): print(f"处理测试事件: {event.event_id[:8]}, 数据: {event.data}") time.sleep(0.1) # 测试订阅和发布 event_center.subscribe(EventType.TEST_EVENT, test_handler) test_event = Event( type=EventType.TEST_EVENT, source="test_script", data={"message": "Hello EventCenter"}, token="test_token" ) event_center.publish(test_event) time.sleep(0.5) # 测试统计功能 print("事件中心统计:", event_center.get_stats())
最新发布
08-20
self._stats['failed_events'] += 1 return True # 成功时返回True except Exception: return False # 失败时返回False 修改为： try: event.__post_init__() # 验证事件数据 except Exception as e: ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值