The data in this instance is transient; no backup or replication will be required. It is currently under performing.
The database size is static and including indexes is 19G.
Total system memory is 32G.
After profiling the system, you highlight these MySQL status and global variables:
The OS metrics indicate that disk is a bottleneck.
Other variables retain their default values.
Which two changes will provide the most benefit to the instance? (Choose two.)
Increasing the innodb_log_file_size to 1G would help because the database size is relatively large, and the default log file size may lead to frequent file rotations, causing performance issues. Disabling the innodb_doublewrite can also improve performance since, despite the potential risk of data corruption, it reduces the I/O overhead, which is stated as a bottleneck. Additionally, the doublewrite buffer isn't necessary if disk performance is a critical issue and data durability is not prioritized in this context. Adjusting these parameters would provide the most significant performance benefit for the given scenario.
AD and not E, trx 1 uses more io than 2. max connections and memory are fine also.
Not A, binlog is off. Not B. max_connections has nothing to do with it. C. innodb_log_file_size --- yes. The default value is 50 megs. This file filling up could cause rollbacks from aborted queries. D. innodb_doublewrite=0 -- yes. Not E. 1 is actually worse. Not F. We have more memory than data. So C and D.
this question is the same with number 4.
Although data is written twice, the doublewrite buffer does not require twice as much I/O overhead or twice as many I/O operations