11gR2 ASM優先映象讀取測試
優先映象讀取測試
首先設定ASM首選映象
SQL> alter system set ASM_PREFERRED_READ_FAILURE_GROUPS=’DATA.DATA_0000′ sid=’+ASM1′;
SQL> alter system set ASM_PREFERRED_READ_FAILURE_GROUPS=’DATA.DATA_0001′ sid=’+ASM2′;
檢查設定:
一節點:
SQL> select group_number,disk_number,preferred_read from v$asm_disk where group_number=1;
GROUP_NUMBER DISK_NUMBER P
------------ ----------- -
1 1 N
1 0 Y
二節點:
SQL> select group_number,disk_number,preferred_read from v$asm_disk where group_number=1;
GROUP_NUMBER DISK_NUMBER P
------------ ----------- -
1 1 Y
1 0 N
為測試的精準性,重啟CRS服務程式後進行相關測試:
一節點:
檢視對應的磁碟讀寫(未進行任何讀寫操作):
一節點:
select instname,disk_number,failgroup,reads,read_time from v$asm_disk_iostat where instname='ora11g1';
SQL>select instname,disk_number,failgroup,reads,read_time from v$asm_disk_iostat where instname='ora11g1'
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g1 0 DATA_0000 3686 70.533591
ora11g1 1 DATA_0001 0 0
目前一節點在DATA_0000上的讀IO是3686
二節點:
SQL> select instname,disk_number,failgroup,reads,read_time from v$asm_disk_iostat where instname='ora11g2';
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g2 0 DATA_0000 1 .024885
ora11g2 1 DATA_0001 5868 56.486877
目前二節點在DATA_0001上的讀IO是5868
接下來做的操作是針對IO,在一節點上查詢test使用者下的test表,然後重新整理buffer_cache重新在二節點執行該查詢操作
一節點執行:
SQL> select count(*) from test.test;
COUNT(*)
----------
9170264
SQL> select instname,disk_number,failgroup,reads,read_time from v$asm_disk_iostat where instname='ora11g1';
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g1 0 DATA_0000 4857 109.763665
ora11g1 1 DATA_0001 0 0
從沒有執行之前的3686增加到4857增加了增加1171個資料塊
二節點:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g2 0 DATA_0000 1 .024885
ora11g2 1 DATA_0001 6035 61.388466
增加了167個資料塊,增加不明顯。
可以明顯看到,ora11g1例項對應的IO基本在DATA_0000 DATA_0001 IO增量不大。
重新整理雙節點buffer:
一節點:
SQL> alter system flush buffer_cache;
System altered.
二節點:
SQL> alter system flush buffer_cache;
System altered.
檢視雙節點IO情況:
一節點:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g1 0 DATA_0000 5202 125.504934
ora11g1 1 DATA_0001 0 0
二節點:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g2 0 DATA_0000 1 .024885
ora11g2 1 DATA_0001 6867 80.835627
二節點做查詢後檢視IO情況:
一節點IO:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g1 0 DATA_0000 5460 129.884158
ora11g1 1 DATA_0001 0 0
二節點IO:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g2 0 DATA_0000 1 .024885
ora11g2 1 DATA_0001 8233 124.786551
二節點IO增量在1366 一節點IO增量在200左右,二節點增量較大
結論,從目前的手段來看,針對於優先映象讀取測試的話,從目前手段來看很難看出在一節點上操作時,DATA_0001 磁碟的IO是否是不受一節點操作影響的
雖然從IO增量上來看!結論似乎沒有問題
------------------------------------------------------------------------------------
原部落格地址:http://blog.itpub.net/23732248/
原作者:應以峰 (frank-ying)
-------------------------------------------------------------------------------------
首先設定ASM首選映象
SQL> alter system set ASM_PREFERRED_READ_FAILURE_GROUPS=’DATA.DATA_0000′ sid=’+ASM1′;
SQL> alter system set ASM_PREFERRED_READ_FAILURE_GROUPS=’DATA.DATA_0001′ sid=’+ASM2′;
檢查設定:
一節點:
SQL> select group_number,disk_number,preferred_read from v$asm_disk where group_number=1;
GROUP_NUMBER DISK_NUMBER P
------------ ----------- -
1 1 N
1 0 Y
二節點:
SQL> select group_number,disk_number,preferred_read from v$asm_disk where group_number=1;
GROUP_NUMBER DISK_NUMBER P
------------ ----------- -
1 1 Y
1 0 N
為測試的精準性,重啟CRS服務程式後進行相關測試:
一節點:
檢視對應的磁碟讀寫(未進行任何讀寫操作):
一節點:
select instname,disk_number,failgroup,reads,read_time from v$asm_disk_iostat where instname='ora11g1';
SQL>select instname,disk_number,failgroup,reads,read_time from v$asm_disk_iostat where instname='ora11g1'
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g1 0 DATA_0000 3686 70.533591
ora11g1 1 DATA_0001 0 0
目前一節點在DATA_0000上的讀IO是3686
二節點:
SQL> select instname,disk_number,failgroup,reads,read_time from v$asm_disk_iostat where instname='ora11g2';
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g2 0 DATA_0000 1 .024885
ora11g2 1 DATA_0001 5868 56.486877
目前二節點在DATA_0001上的讀IO是5868
接下來做的操作是針對IO,在一節點上查詢test使用者下的test表,然後重新整理buffer_cache重新在二節點執行該查詢操作
一節點執行:
SQL> select count(*) from test.test;
COUNT(*)
----------
9170264
SQL> select instname,disk_number,failgroup,reads,read_time from v$asm_disk_iostat where instname='ora11g1';
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g1 0 DATA_0000 4857 109.763665
ora11g1 1 DATA_0001 0 0
從沒有執行之前的3686增加到4857增加了增加1171個資料塊
二節點:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g2 0 DATA_0000 1 .024885
ora11g2 1 DATA_0001 6035 61.388466
增加了167個資料塊,增加不明顯。
可以明顯看到,ora11g1例項對應的IO基本在DATA_0000 DATA_0001 IO增量不大。
重新整理雙節點buffer:
一節點:
SQL> alter system flush buffer_cache;
System altered.
二節點:
SQL> alter system flush buffer_cache;
System altered.
檢視雙節點IO情況:
一節點:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g1 0 DATA_0000 5202 125.504934
ora11g1 1 DATA_0001 0 0
二節點:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g2 0 DATA_0000 1 .024885
ora11g2 1 DATA_0001 6867 80.835627
二節點做查詢後檢視IO情況:
一節點IO:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g1 0 DATA_0000 5460 129.884158
ora11g1 1 DATA_0001 0 0
二節點IO:
INSTNAME DISK_NUMBER FAILGROUP READS READ_TIME
---------------------------------------------------------------- ----------- ------------------------------ ---------- ----------
ora11g2 0 DATA_0000 1 .024885
ora11g2 1 DATA_0001 8233 124.786551
二節點IO增量在1366 一節點IO增量在200左右,二節點增量較大
結論,從目前的手段來看,針對於優先映象讀取測試的話,從目前手段來看很難看出在一節點上操作時,DATA_0001 磁碟的IO是否是不受一節點操作影響的
雖然從IO增量上來看!結論似乎沒有問題
------------------------------------------------------------------------------------
原部落格地址:http://blog.itpub.net/23732248/
原作者:應以峰 (frank-ying)
-------------------------------------------------------------------------------------
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/23732248/viewspace-1407743/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 優先佇列的效能測試佇列
- Oracle ASM (10) - ASM中優先讀failure group配置ASM_PREFERRED_READ_FAILURE_GROUPSOracleASMAI
- Oracle ASM (11) - ASM中優先讀failure group配置ASM_PREFERRED_READ_FAILURE_GROUPSOracleASMAI
- 放棄測試優先式開發(TDD)
- 使用測試優先方法開發使用者介面
- 容器映象拉取不了,不防試試這個公益映象倉庫
- asm中template特性測試!ASM
- nginx快取優先順序Nginx快取
- spring boot學習(6)— 配置資訊及其讀取優先順序Spring Boot
- 測試流程規範--測試准入、準出、停止標準、bug優先順序定義
- Oracle 11gRac 測試案例(五)ASM功能測試OracleASM
- Flex ASM自動重定位ASM例項測試FlexASM
- oracle 11gr2 drop asmOracleASM
- 關於瀏覽器快取問題(圖片更換後,頁面仍優先讀取快取)瀏覽器快取
- JVM載入TimeZone讀取檔案優先順序實戰分析JVM
- 【ASM】Oracle ASM + 11gR2 + RHEL6.5 安裝ASMOracle
- 11gR2 RAC ASM 啟動ASM
- 【自動化測試】Python 讀取 .ini 格式檔案Python
- MicrosoftEdge同源策略不嚴導致任意檔案讀取測試ROS
- 美團二面:SpringBoot讀取配置優先順序順序是什麼?Spring Boot
- 部署rabbitMQ映象叢集實戰測試MQ
- Tinder在印度測試最新功能 女士可以優先選擇約會物件物件
- dd模擬asm磁碟容災測試ASM
- ASM資料庫的一個測試ASM資料庫
- 效能測試之測試分析與調優
- 搶先測試如何改變遊戲產業遊戲產業
- 11GR2新特性測試-閃迴歸檔
- oracle 11gR2 RAC 撥公網物理測試Oracle
- ORACLE 11gr2 ASM redo log 增加OracleASM
- 介面測試讀取 Excel 中引數返回值全部錯誤Excel
- Mysql取隨機資料效率測試(400W條中讀取100條)MySql隨機
- xbbed一鍵讀取ASM block到檔案系統ASMBloC
- sqlldr效能調優測試SQL
- 11gR2 RAC ASM啟動過程ASM
- solaris10_oracle10g_asm_non_asm遷移資料庫測試OracleASM資料庫
- Kotlin慣用語法(優先推薦閱讀)Kotlin
- 介面自動化測試:引數化封裝(excel檔案讀取)封裝Excel
- 有名訊號量實現讀者-寫者問題(讀者優先)