AWS prescriptive-guidance documentation change
Summary
Updated documentation formatting: fixed whitespace in sysbench commands, converted section headers to markdown headings, reformatted performance data tables, and replaced image references with new paths.
Security assessment
Changes involve formatting improvements, whitespace cleanup, and image path updates without any security-related content. No vulnerabilities, security practices, or security features are mentioned or modified.
Diff
diff --git a/prescriptive-guidance/latest/archiving-mysql-data/appendix-ii.md b/prescriptive-guidance/latest/archiving-mysql-data/appendix-ii.md index 7f59990de..dc65d3e3a 100644 --- a//prescriptive-guidance/latest/archiving-mysql-data/appendix-ii.md +++ b//prescriptive-guidance/latest/archiving-mysql-data/appendix-ii.md @@ -6,0 +7,2 @@ +Archiving a table that has no primary key and only one index (no load on the database)Archiving a table that has a primary key (no load on the database)Archiving table that has a primary key (with load on the database) + @@ -14,2 +16,2 @@ The following sysbench commands were used to prepare and run the load on the dat - sysbench oltp_read_write --db-driver=mysql --mysql-db=<DATABASE> --mysql-user=<USER> --mysql-password=<PASSWORD> --mysql-host=<ENDPOINT> --tables=1000 --table-size=2000000 --threads=500 prepare - sysbench oltp_read_write --db-driver=mysql --mysql-db=<DATABASE> --mysql-user=<USER> --mysql-password=<PASSWORD> --mysql-host=<ENDPOINT> --tables=1000 --rate=500 --threads=500 run + sysbench oltp_read_write --db-driver=mysql --mysql-db=<DATABASE> --mysql-user=<USER> --mysql-password=<PASSWORD> --mysql-host=<ENDPOINT> --tables=1000 --table-size=2000000 --threads=500 prepare + sysbench oltp_read_write --db-driver=mysql --mysql-db=<DATABASE> --mysql-user=<USER> --mysql-password=<PASSWORD> --mysql-host=<ENDPOINT> --tables=1000 --rate=500 --threads=500 run @@ -17 +19 @@ The following sysbench commands were used to prepare and run the load on the dat -**Archiving a table that has no primary key and only one index (no load on the database)** +## Archiving a table that has no primary key and only one index (no load on the database) @@ -21,5 +23,5 @@ The following sysbench commands were used to prepare and run the load on the dat - Action Count Time Pct - commit 600050 1715.3582 83.31 - select 300025 166.5470 8.09 - inserting 300024 165.4025 8.03 - other 0 11.6644 0.57 + Action Count Time Pct + commit 600050 1715.3582 83.31 + select 300025 166.5470 8.09 + inserting 300024 165.4025 8.03 + other 0 11.6644 0.57 @@ -29 +31 @@ It took around 34 minutes to archive 300,024 rows. This table had 2 million rows -**Archiving a table that has a primary key (no load on the database)** +## Archiving a table that has a primary key (no load on the database) @@ -33,5 +35,5 @@ It took around 34 minutes to archive 300,024 rows. This table had 2 million rows - Action Count Time Pct - commit 4000000 11065.9534 82.16 - select 2000000 1278.1854 9.49 - inserting 1999999 1050.4961 7.80 - other 0 74.1519 0.55 + Action Count Time Pct + commit 4000000 11065.9534 82.16 + select 2000000 1278.1854 9.49 + inserting 1999999 1050.4961 7.80 + other 0 74.1519 0.55 @@ -43 +45,3 @@ The following graph shows that pt-archiver consumes very little CPU and resource - + + + @@ -45 +49 @@ The following graph shows that pt-archiver consumes very little CPU and resource -**Archiving table that has a primary key (with load on the database)** +## Archiving table that has a primary key (with load on the database) @@ -49,5 +53,5 @@ The following graph shows that pt-archiver consumes very little CPU and resource - Action Count Time Pct - commit 4000000 19688.8362 56.23 - inserting 1999999 13933.4418 39.79 - select 2000000 1305.1770 3.73 - other 0 89.1787 0.25 + Action Count Time Pct + commit 4000000 19688.8362 56.23 + inserting 1999999 13933.4418 39.79 + select 2000000 1305.1770 3.73 + other 0 89.1787 0.25 @@ -59 +63,3 @@ The following graph shows that during the test, the CPU utilization was up to 15 - + + +