硬件级别的优化

Optimizing at the Hardware Level

Any database application eventually hits hardware limits as the database becomes more and more busy. A DBA must evaluate whether it is possible to tune the application or reconfigure the server to avoid thesebottlenecks, or whether more hardware resources are required. System bottlenecks typically arise from these sources:                                       --应用程序接近硬件限制，dba需要评估是调整应用或者调整数据库配置，还是升级硬件，取决于以下因素：

• Disk seeks. It takes time for the disk to find a piece of data. With modern disks, the mean time for this is usually lower than 10ms, so we can in theory do about 100 seeks a second. This time improves slowly with new disks and is very hard to optimize for a single table. The way to optimize seek time is to distribute the data onto more than one disk.         --磁盘查找：换新硬盘来提高查找速度效果不大，提高查询速度的最好方法是将数据分布到多个磁盘上。

• Disk reading and writing. When the disk is at the correct position, we need to read or write the data. With modern disks, one disk delivers at least 10–20MB/s throughput. This is easier to optimize than seeks because you can read in parallel from multiple disks.    --磁盘读写：并行读取磁盘比优化更有效率

• CPU cycles. When the data is in main memory, we must process it to get our result. Having small tables compared to the amount of memory is the most common limiting factor. But with small tables, speed is usually not the problem.    --CPU周期：小表耗内存，但处理速度快。

• Memory bandwidth. When the CPU needs more data than can fit in the CPU cache, main memory bandwidth becomes a bottleneck. This is an uncommon bottleneck for most systems, but one to be aware of.    --内存带宽：