Mechanical hard disk IO include: seek, rotation, transfer
That sounds like the SSD IO transfer, not seek, rotate
With mechanical drive the design of the database to immediately IO and debris is concerned, if with solid-state drives are the main need not pay attention to these problems, think for a few days also baidu also a few days and there is no definite answer, who can give advice or comments!

CodePudding user response:

Do you want to many, this is one of the characteristics of the software thought, has nothing to do with the type of hard disk,

CodePudding user response:

reference 1st floor AHUA1001 response:

do you want to much, this is one of the characteristics of the software thought, has nothing to do with the type of hard disk,

You don't understand what I ask

CodePudding user response:

Before I have a feeling that with mechanical drive on their own DB server should pay great attention to the order when IO and debris, ali and tencent now cloud database with all SSD, when designing the database these don't have to care about

CodePudding user response:

Order IO said the db file sequential read? What pieces? Because of space problem caused by the delete?

CodePudding user response:

Machine hard disk, the data distribution in the disk outer ring's true as far as possible when rebalance (ASM automatically starting from the outer ring as far as possible put data), generally speaking, the disk is full, it can provide the overall performance of the worse,

CodePudding user response:

reference 4 floor minsic78 response:

order IO said the db file sequential read? What pieces? Because of space problem caused by the delete?

Order IO read write and order, including order immediately reduce fragmentation is the purpose of IO,

CodePudding user response:

refer to 6th floor old white 2018 response:

Quote: refer to 4th floor minsic78 response:

Order IO said the db file sequential read? What pieces? Because of space problem caused by the delete?

Order IO read write and order, including order immediately reduce fragmentation is the purpose of IO,

Want to reduce the random IO, the best optimization is what all don't run on the database, and of course this is not possible, so the optimal random IO is the best way to optimize your SQL