TimesTen 应用层数据库缓存学习:11. AWT性能监控

2024-02-04 13:48

本文主要是介绍TimesTen 应用层数据库缓存学习:11. AWT性能监控,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

演示环境准备

为了运行以下的例子,我们建立了一个AWT缓存组
Oracle Schema用户:

$ sqlplus tthr/oracle@ttorcl
create table orders(ord_num int primary key, ship_time timestamp not null);
grant select, insert, update, delete on orders to cacheadm;

TimesTen Cache管理用户:

cacheadm>
CREATE ASYNCHRONOUS WRITETHROUGH CACHE GROUP "AWT" FROM"TTHR"."ORDERS" ("ORD_NUM"   NUMBER(38)   NOT NULL,"SHIP_TIME" TIMESTAMP(6) NOT NULL,PRIMARY KEY("ORD_NUM"))
cacheadm> call ttrepstart;
cacheadm> cachegroups;Cache Group CACHEADM.AWT:Cache Group Type: Asynchronous WritethroughAutorefresh: NoAging: No aging definedRoot Table: TTHR.ORDERSTable Type: Propagate1 cache group found.cacheadm>repschemes;Replication Scheme TTREP._AWTREPSCHEME:Element: _1798096                       Type: Table TTHR.ORDERSMaster Store: CACHEDB1_1122 on TIMESTEN-HOL Transmit DurableSubscriber Store: _ORACLE from TIMESTEN-HOL Store: CACHEDB1_1122 on TIMESTEN-HOLPort: (auto)Log Fail Threshold: (none)Retry Timeout: 120 secondsCompress Traffic: DisabledStore: _ORACLE from TIMESTEN-HOLPort: (auto)Log Fail Threshold: (none)Retry Timeout: 120 secondsCompress Traffic: Disabled1 replication scheme found.

OS用户,下面的输出类似于repschems

$ ttrepadmin -showconfig cachedb1_1122Self host "TIMESTEN-HOL", port auto, name "CACHEDB1_1122", LSN 19/2685192, timeout 120, threshold 0
List of subscribers
-------------------Peer name         Host name                 Port    State  Proto Track
----------------  ------------------------ ------  ------- ----- -----
_ORACLE           TIMESTEN-HOL              Auto   Start      38     0Last Msg Sent Last Msg Recv Latency TPS     RecordsPS     
------------- ------------- ------- ------- ---------     
00:00:05      -               -1.00      -1        -1 List of objects and subscriptions
---------------------------------Table details
-------------
Table : TTHR.ORDERS   Timestamp updates : -  Master Name               Subscriber name         
-----------               ---------------         
CACHEDB1_1122             _ORACLE                 

TimesTen Schema用户:

tthr>
insert into orders values(1, sysdate);
ALTER SESSION SET PLSQL_TIMEOUT = 0;
declare ord_num number;      
begin
for i in 1..1000 loop
select max(ord_num) into ord_num from orders;
insert into orders values(ord_num+1, sysdate);
commit;
dbms_lock.sleep( 1 );
end loop;
end;
/

打开 AWT 性能监控

使用ttCacheAWTMonitorConfig打开监控,然后可以用ttRepAdmin查看监控信息。
其中On表示打开,数字16表示16次采样一次,是推荐值,但在我们的例子中,我们采用1,即每次都采样

cacheadm>CALL ttCacheAWTMonitorConfig;
< OFF, 0 >
1 row found.
cacheadm>CALL ttCacheAWTMonitorConfig('off');
< OFF, 0 >
1 row found.
cacheadm>CALL ttCacheAWTMonitorConfig('on');
< ON, 16 >
1 row found.
cacheadm>CALL ttCacheAWTMonitorConfig('on', 1);
< ON, 1 >
1 row found.
cacheadm>CALL ttCacheAWTMonitorConfig;
< ON, 1 >
1 row found.

Display AWT performance results with the ttRepAdmin utility

使用ttRepAdmin的-awtmoninfo 和 -showstatus 选项,例如

$ ttRepAdmin -showstatus -awtmoninfo cachedb1_1122Replication Agent Status as of: 2016-04-21 18:04:39DSN                         : cachedb1_1122
Process ID                  : 8089 (Started)
Replication Agent Policy    : manual
Host                        : TIMESTEN-HOL
RepListener Port            : 42901 (AUTO)
Last write LSN              : 18.65272072
Last LSN forced to disk     : 18.65271808
Replication hold LSN        : 18.65206536Replication Peers:Name                     : _ORACLEHost                     : TIMESTEN-HOLPort                     : 42901 (AUTO) (Connected)Replication State        : STARTEDCommunication Protocol   : 38Name                     : CACHEDB1_1122Host                     : TIMESTEN-HOLPort                     : 0 (AUTO)Replication State        : STARTEDCommunication Protocol   : 38TRANSMITTER thread(s):For                     : _ORACLE (track 0)Start/Restart count   : 1Send LSN              : 18.65245448Transactions sent     : 467Total packets sent    : 856Tick packets sent     : 384MIN sent packet size  : 64MAX sent packet size  : 893AVG sent packet size  : 291Last packet sent at   : 18:04:39Total Packets received: 854MIN rcvd packet size  : 64MAX rcvd packet size  : 120AVG rcvd packet size  : 119Last packet rcvd'd at : 18:04:39TXNs Allocated        : 11TXNs In Use           : 5ACTs Allocated        : 11ACTs In Use           : 5ACTs Data Allocated   : 880Timeout               : 120Adapted Timeout Max   : 120Adapted Timeout Time  : 1461285423current txn           : 0.0Longest batch runtime : 0Longest batch 1st txn : 0.0Longest batch lst txn : 0.0Largest txn (ops)     : 1461231493.12371Largest txn (#ops)    : 1Longest txn (time)    : 0.0Longest txn (secs)    : 0Most recent errors (max 5):TT16025 in repagent.c (line 1227) at 17:34:49 on 04-21-2016TT16285 in transmitter.c (line 1109) at 17:34:49 on 04-21-2016TT16999 in transmitter.c (line 1447) at 17:34:49 on 04-21-2016RECEIVER thread(s):For                     : CACHEDB1_1122 (track 0)Start/Restart count   : 1Transactions received : 467Total packets sent    : 855Tick packets sent     : 0MIN sent packet size  : 64MAX sent packet size  : 120AVG sent packet size  : 119Last packet sent at   : 18:04:39Total Packets received: 2259MIN rcvd packet size  : 64MAX rcvd packet size  : 298AVG rcvd packet size  : 110Last packet rcvd'd at : 18:04:39rxWaitCTN             : 0.0prevCTN               : 0.0current txn           : 0.0serial CTN            : 0.0STA Blk Data Allocated: 32STA Data Allocated    : 4096Longest batch runtime : 0Longest batch 1st txn : 0.0Longest batch lst txn : 0.0Largest txn (ops)     : 1461231493.12371Largest txn (#ops)    : 5Longest txn (time)    : 0.0Longest txn (secs)    : 0AWT Monitoring statistics-------------------------TimesTen processing time : 138.387000 millisecs (100 %)Oracle execute  (SQL execution) time : 0.000000 millisecs (0 %)Oracle execute (PL/SQL execution) time : 0.000000 millisecs (0 %)Time since monitoring was started: 375830.816000 millisecsCacheAwtMethod mode : 1Cache-connect Operational Stats :SQL Operations sent to Oracle : 0Number of update operations : 0Number of update batches    : 0Number of insert operations : 0Number of insert batches    : 0Number of delete operations : 0Number of delete batches    : 0Total number of batches sent: 0Number of bytes sent : 0PL/SQL Operations sent to Oracle : 0Number of update operations : 0Number of insert operations : 0Number of delete operations : 0Number of batches sent : 0Number of bytes sent : 0Number of TimesTen Transactions sent to Oracle (includes retries) : 376Number of retries on TimesTen due to errors on Oracle : 0Number of round trips to Oracle (includes executes, commits and rollbacks) : 0Number of commits on Oracle : 0Number of rollbacks on Oracle : 0Number of rxbatches: 376Number of rxskips: 0Most recent errors (max 5):TT16025 in repagent.c (line 1227) at 17:34:49 on 04-21-2016

注意AWT Monitoring statistics部分。

Using system tables to monitor AWT operations

查询SYS.MONITOR的LAST_LOG_FILE, REPHOLD_LOG_FILE 和 REPHOLD_LOG_OFF列。
它们的含义为:
- LAST_LOG_FILE: Most recent log file present
- REPHOLD_LOG_FILE: Number of last log file held by replication
- REPHOLD_LOG_OFF: Offset in last log file held by replication

SYS.MONITOR只有一行记录, 输出中的18表示log文件是cachedb1_1122.log18

cacheadm>select LAST_LOG_FILE, REPHOLD_LOG_FILE, REPHOLD_LOG_OFF from SYS.MONITOR;
< 18, 18, 63803656 >
1 row found.
cacheadm>select LAST_LOG_FILE, REPHOLD_LOG_FILE, REPHOLD_LOG_OFF from SYS.MONITOR;
< 18, 18, 63854856 >
1 row found.
cacheadm>select LAST_LOG_FILE, REPHOLD_LOG_FILE, REPHOLD_LOG_OFF from SYS.MONITOR;
< 18, 18, 63854856 >
1 row found.

依据下面的原则来判断是非有问题,即如果复制hold的日志文件和产生的最新日志文件差距不断拉大,则表示复制数据的速度赶不上产生数据的速度

If the difference between the value in the LAST_LOG_FILE column and the value in the REPHOLD_LOG_FILE column is increasing over time, and the value in the REPHOLD_LOG_OFF column is increasing slowly or not changing, then the tables are being updated at a faster rate than the updates are being replicated.

如果有问题,可以结合以下的命令再判断

$ ttRepAdmin -receiver -list cachedb1_1122
Peer name         Host name                 Port    State  Proto Track
----------------  ------------------------ ------  ------- ----- -----
_ORACLE           TIMESTEN-HOL              Auto   Start      38     0Last Msg Sent Last Msg Recv Latency TPS     RecordsPS Logs
------------- ------------- ------- ------- --------- ----
00:00:04      -               -1.00      -1        -1    1

这篇关于TimesTen 应用层数据库缓存学习:11. AWT性能监控的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



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

相关文章

SpringBoot实现数据库读写分离的3种方法小结

《SpringBoot实现数据库读写分离的3种方法小结》为了提高系统的读写性能和可用性,读写分离是一种经典的数据库架构模式,在SpringBoot应用中,有多种方式可以实现数据库读写分离,本文将介绍三... 目录一、数据库读写分离概述二、方案一:基于AbstractRoutingDataSource实现动态

C# WinForms存储过程操作数据库的实例讲解

《C#WinForms存储过程操作数据库的实例讲解》:本文主要介绍C#WinForms存储过程操作数据库的实例,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一、存储过程基础二、C# 调用流程1. 数据库连接配置2. 执行存储过程(增删改)3. 查询数据三、事务处

Python如何使用__slots__实现节省内存和性能优化

《Python如何使用__slots__实现节省内存和性能优化》你有想过,一个小小的__slots__能让你的Python类内存消耗直接减半吗,没错,今天咱们要聊的就是这个让人眼前一亮的技巧,感兴趣的... 目录背景:内存吃得满满的类__slots__:你的内存管理小助手举个大概的例子:看看效果如何?1.

mysql数据库重置表主键id的实现

《mysql数据库重置表主键id的实现》在我们的开发过程中,难免在做测试的时候会生成一些杂乱无章的SQL主键数据,本文主要介绍了mysql数据库重置表主键id的实现,具有一定的参考价值,感兴趣的可以了... 目录关键语法演示案例在我们的开发过程中,难免在做测试的时候会生成一些杂乱无章的SQL主键数据,当我们

Spring Boot 整合 MyBatis 连接数据库及常见问题

《SpringBoot整合MyBatis连接数据库及常见问题》MyBatis是一个优秀的持久层框架,支持定制化SQL、存储过程以及高级映射,下面详细介绍如何在SpringBoot项目中整合My... 目录一、基本配置1. 添加依赖2. 配置数据库连接二、项目结构三、核心组件实现(示例)1. 实体类2. Ma

Linux修改pip和conda缓存路径的几种方法

《Linux修改pip和conda缓存路径的几种方法》在Python生态中,pip和conda是两种常见的软件包管理工具,它们在安装、更新和卸载软件包时都会使用缓存来提高效率,适当地修改它们的缓存路径... 目录一、pip 和 conda 的缓存机制1. pip 的缓存机制默认缓存路径2. conda 的缓

Redis中高并发读写性能的深度解析与优化

《Redis中高并发读写性能的深度解析与优化》Redis作为一款高性能的内存数据库,广泛应用于缓存、消息队列、实时统计等场景,本文将深入探讨Redis的读写并发能力,感兴趣的小伙伴可以了解下... 目录引言一、Redis 并发能力概述1.1 Redis 的读写性能1.2 影响 Redis 并发能力的因素二、

Redis解决缓存击穿问题的两种方法

《Redis解决缓存击穿问题的两种方法》缓存击穿问题也叫热点Key问题,就是⼀个被高并发访问并且缓存重建业务较复杂的key突然失效了,无数的请求访问会在瞬间给数据库带来巨大的冲击,本文给大家介绍了Re... 目录引言解决办法互斥锁(强一致,性能差)逻辑过期(高可用,性能优)设计逻辑过期时间引言缓存击穿:给

查看Oracle数据库中UNDO表空间的使用情况(最新推荐)

《查看Oracle数据库中UNDO表空间的使用情况(最新推荐)》Oracle数据库中查看UNDO表空间使用情况的4种方法:DBA_TABLESPACES和DBA_DATA_FILES提供基本信息,V$... 目录1. 通过 DBjavascriptA_TABLESPACES 和 DBA_DATA_FILES

Java实现数据库图片上传与存储功能

《Java实现数据库图片上传与存储功能》在现代的Web开发中,上传图片并将其存储在数据库中是常见的需求之一,本文将介绍如何通过Java实现图片上传,存储到数据库的完整过程,希望对大家有所帮助... 目录1. 项目结构2. 数据库表设计3. 实现图片上传功能3.1 文件上传控制器3.2 图片上传服务4. 实现