{"id":105503,"date":"2025-02-27T20:13:41","date_gmt":"2025-02-27T20:13:41","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/?p=105503"},"modified":"2025-02-06T20:23:10","modified_gmt":"2025-02-06T20:23:10","slug":"mysql-shell-basic-configuration-management-part-3-disk-i-o-and-storage-optimization","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/databases\/mysql\/mysql-shell-basic-configuration-management-part-3-disk-i-o-and-storage-optimization\/","title":{"rendered":"MySQL Shell Basic Configuration Management (Part 3 \u2013 Disk I\/O and Storage Optimization)"},"content":{"rendered":"

This is part of a series of posts from Chisom Kanu about using MySQL Shell in the management of MySQL. You can see the entire series here<\/a>.<\/p>\n\n

So far, in our previous articles on MySQL optimization, we’ve looked at basic configuration management<\/a> and memory and CPU<\/a> tuning using MySQL Shell. In the first article, we looked into how to optimize your MySQL database\u2019s configuration with MySQL Shell. In the second article, we focused on memory and CPU usage, showing how to monitor and improve performance by adjusting important settings. In this third installment in the series, we’ll continue our series by going into another important aspect of database optimization\u2014disk I\/O<\/a> and storage.<\/p>\n

Disk I\/O plays an important role in how fast MySQL can read and write data. Even if your memory and CPU are optimized, poor disk I\/O performance can cause issues in the entire system. This is especially important for write-heavy databases or those handling large datasets, as the speed of disk operations can dramatically affect overall performance. InnoDB<\/a>, the default storage engine in MySQL, is highly reliant on efficient disk I\/O. By tweaking its settings, you can reduce latency and improve throughput. We will cover the essential MySQL Shell commands and scripts to monitor, configure, and optimize your disk I\/O and storage for maximum performance.<\/p>\n

We begin by accessing MySQL Shell. If you\u2019ve been following along in this series, you\u2019re likely familiar with how to do this. But just to make sure we\u2019re on the same page, here\u2019s how to get started. Open your terminal and type:<\/p>\n

mysqlsh --uri root@localhost<\/pre>\n
If you need to enter a password, you’ll be prompted.. If you’re unsure about connection details, please refer back to Part 1 of this series<\/a>.<\/p>\n
Note that this will connect with the very powerful root user, so be careful doing this on a production server if you are not sure what you are doing.<\/em><\/p>\n
After connecting, switch to JavaScript mode (since we\u2019ll be using JavaScript commands in MySQL Shell) by typing \\js<\/code>. Now, we\u2019re ready to work with disk I\/O settings.<\/p>\n
<\/a>Why We’re Using MySQL Shell<\/h2>\n
Now, you might be wondering, “Can’t we just run SQL commands to do most of what is in this article?” And you’re right, in many cases we could. But MySQL Shell offers several advantages that make our optimization journey smoother:<\/p>\n