AWS prescriptive-guidance documentation change
Summary
Updated example metrics and removed redundant Oracle documentation reference.
Security assessment
Content clarification and example update. No security implications, vulnerability references, or security features documented.
Diff
diff --git a/prescriptive-guidance/latest/oracle-exadata-blueprint/storage-indexes.md b/prescriptive-guidance/latest/oracle-exadata-blueprint/storage-indexes.md index 77df3ce03..54d2b3829 100644 --- a//prescriptive-guidance/latest/oracle-exadata-blueprint/storage-indexes.md +++ b//prescriptive-guidance/latest/oracle-exadata-blueprint/storage-indexes.md @@ -20 +20 @@ The following database statistics help assess the benefits of storage indexes in -For more information about these, see the [Oracle documentation](https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-storage-server-monitoring.html#GUID-BBCE8F29-F939-4E06-89D5-947C41798CF8). In the following example from an AWR report collected from an Exadata system, 5.4 Gbps of read operations were Smart Scan eligible. 4.6 Gbps of those I/O operations were processed by cells before predicate offloading, and 55 MBps were returned to the compute nodes with a savings of 820 MBps I/O by storage index. In this example, the dependency on the storage index isn't very high. +In the following example from an AWR report collected from an Exadata system, 5.4 Gbps of read operations were Smart Scan eligible. 4.6 Gbps of those I/O operations were processed by cells before predicate offloading, and 55 MBps were returned to the compute nodes with a savings of 820 MBps I/O by storage index. In this example, the dependency on the storage index isn't very high.