文档首页
MySQL 8.4 参考手册
8.4 中文镜像

MySQL 8.4 参考手册 · 中文镜像

正文为中文,英文原文默认隐藏。点击任意中文段落即可展开 / 收起对应英文原文。

打开官方英文原文 ↗

译文由机器翻译生成,仅供理解参考;有疑问请以官方英文原文为准。

中文点击中文段落可显示 / 隐藏英文原文本页译文覆盖 100%

29.12.3 性能模式实例表29.12.3 Performance Schema Instance Tables

实例表记录了被监控对象的类型。它们提供事件名称以及解释性注释或状态信息:Instance tables document what types of objects are instrumented. They provide event names and explanatory notes or status information:

这些表列出了被检测的同步对象、文件和连接。有三种类型的同步对象:cond、mutex和rwlock。每个实例表都有一个EVENT_NAME或NAME列,用于指示与每行相关的检测器。检测器名称可能包含多个部分,并形成层次结构,如第 29.6 节,“Performance Schema 检测器命名约定”所述。These tables list instrumented synchronization objects, files, and connections. There are three types of synchronization objects: cond, mutex, and rwlock. Each instance table has an EVENT_NAME or NAME column to indicate the instrument associated with each row. Instrument names may have multiple parts and form a hierarchy, as discussed in Section 29.6, “Performance Schema Instrument Naming Conventions”.

mutex_instances.LOCKED_BY_THREAD_ID 和 rwlock_instances.WRITE_LOCKED_BY_THREAD_ID 列在调查性能瓶颈或死锁时非常重要。有关如何为此目的使用它们的示例,请参见 第 29.19 节,“使用性能模式诊断问题”The mutex_instances.LOCKED_BY_THREAD_ID and rwlock_instances.WRITE_LOCKED_BY_THREAD_ID columns are extremely important for investigating performance bottlenecks or deadlocks. For examples of how to use them for this purpose, see Section 29.19, “Using the Performance Schema to Diagnose Problems”