AWS prescriptive-guidance documentation change
Summary
Updated author attribution and removed bold formatting from table headers in documentation about estimating RDS engine size using AWR reports.
Security assessment
Changes involve formatting adjustments (removing bold markers) and author attribution updates. No security-related content modifications or references to vulnerabilities/security features were found.
Diff
diff --git a/prescriptive-guidance/latest/patterns/estimate-the-amazon-rds-engine-size-for-an-oracle-database-by-using-awr-reports.md b/prescriptive-guidance/latest/patterns/estimate-the-amazon-rds-engine-size-for-an-oracle-database-by-using-awr-reports.md index ce89a8baf..906126369 100644 --- a//prescriptive-guidance/latest/patterns/estimate-the-amazon-rds-engine-size-for-an-oracle-database-by-using-awr-reports.md +++ b//prescriptive-guidance/latest/patterns/estimate-the-amazon-rds-engine-size-for-an-oracle-database-by-using-awr-reports.md @@ -9 +9 @@ SummaryPrerequisites and limitationsArchitectureToolsBest practicesEpicsRelated - _Created by Abhishek Verma (AWS) and Eduardo Valentim (AWS)_ + _Abhishek Verma and Eduardo Valentim, Amazon Web Services_ @@ -136 +136 @@ Option 1: Use the load profile.| The following table shows an example of the Loa -For more accurate information, we recommend that you use option 2 (I/O profiles) or option 3 (instance activity statistics) instead of the load profile.| ****| **Per Second**| **Per Transaction**| **Per Exec**| **Per Call** +For more accurate information, we recommend that you use option 2 (I/O profiles) or option 3 (instance activity statistics) instead of the load profile.| | Per Second| Per Transaction| Per Exec| Per Call @@ -176 +176 @@ DBA -Option 2: Use instance activity statistics.| If you’re using an Oracle Database version before 12c, you can use the Instance Activity Stats section of the AWR report to estimate IOPS and throughput. The following table shows an example of this section.| **Statistic**| **Total**| **per Second**| **per Trans** +Option 2: Use instance activity statistics.| If you’re using an Oracle Database version before 12c, you can use the Instance Activity Stats section of the AWR report to estimate IOPS and throughput. The following table shows an example of this section.| Statistic| Total| per Second| per Trans @@ -190 +190 @@ DBA -Option 3: Use I/O profiles.| In Oracle Database 12c, the AWR report includes an I/O Profiles section that presents all the information in a single table and provides more accurate data about database performance. The following table shows an example of this section.| ****| **Read+Write Per Second**| **Read per Second**| **Write Per Second** +Option 3: Use I/O profiles.| In Oracle Database 12c, the AWR report includes an I/O Profiles section that presents all the information in a single table and provides more accurate data about database performance. The following table shows an example of this section.| | Read+Write Per Second| Read per Second| Write Per Second @@ -259 +259 @@ Use the following command to count the sockets in the processor. -We don’t recommend using OS commands such as **nmon** and **sar** to extract CPU utilization. This is because those calculations include CPU utilization by other processes and might not reflect the actual CPU that is used by the database.**To estimate available cores by using the AWR report** You can also derive CPU utilization from the first section of the AWR report. Here’s an excerpt from the report.| **DB Name**| **DB Id**| **Instance**| **Inst num**| **Startup Time**| **Release**| **RAC** +We don’t recommend using OS commands such as **nmon** and **sar** to extract CPU utilization. This is because those calculations include CPU utilization by other processes and might not reflect the actual CPU that is used by the database.**To estimate available cores by using the AWR report** You can also derive CPU utilization from the first section of the AWR report. Here’s an excerpt from the report.| DB Name| DB Id| Instance| Inst num| Startup Time| Release| RAC @@ -268 +268 @@ DBA -Option 2: Estimate CPU utilization by using OS statistics.| You can check the OS CPU usage statistics either directly in the OS (using **sar** or another host OS utility) or by reviewing the IDLE/(IDLE+BUSY) values from the Operating System Statistics section of the AWR report. You can see the seconds of CPU consumed directly from **v$osstat**. The AWR and Statspack reports also show this data in the Operating System Statistics section.If there are multiple databases on the same box, they all have the same **v$osstat** values for BUSY_TIME.| **Statistic**| **Value**| **End Value** +Option 2: Estimate CPU utilization by using OS statistics.| You can check the OS CPU usage statistics either directly in the OS (using **sar** or another host OS utility) or by reviewing the IDLE/(IDLE+BUSY) values from the Operating System Statistics section of the AWR report. You can see the seconds of CPU consumed directly from **v$osstat**. The AWR and Statspack reports also show this data in the Operating System Statistics section.If there are multiple databases on the same box, they all have the same **v$osstat** values for BUSY_TIME.| Statistic| Value| End Value @@ -312 +312 @@ DBA -Option 3: Estimate CPU utilization by using database metrics.| If multiple databases are running in the system, you can use the database metrics that appears at the beginning of the report.| ****| **Snap Id**| **Snap Time**| **Sessions**| **Cursors/Session** +Option 3: Estimate CPU utilization by using database metrics.| If multiple databases are running in the system, you can use the database metrics that appears at the beginning of the report.| | Snap Id| Snap Time| Sessions| Cursors/Session @@ -348 +348 @@ Estimate memory requirements by using memory statistics.| You can use the AWR re -**Instance Efficiency Percentages (target 100%)**| **Buffer Nowait %:**| 99.99| **Redo NoWait %:**| 100.00 +**Instance Efficiency Percentages (target 100%)**| Buffer Nowait %:| 99.99| Redo NoWait %:| 100.00 @@ -360 +360 @@ In this example, all the metrics look fine, so you can use the SGA and PGA for t -****| **Begin**| **End** +| Begin| End