MySQL的性能优化文章有很多，这里介绍个通过优化Swap & Memory来提高性能的方法。
The VM for Linux prefers system cache over application memory. What does this mean? The best way I can explain is by example.
Imagine you have 32 GB of RAM
MySQL is set to take 20 GB of RAM for a process based buffer and up to 6M for the various thread buffers.
Over a period of time the box swaps. The only thing that is running is mysql and its memory size is around 21GB for resident memory. Why does swap grow when there is plenty of memory? The reason is when a memory alloc is needed (thread based buffer is tickled) the VM will choose to use swap over allocating from the system cache, when there is not enough free memory.
DO NOT TURN OFF SWAP to prevent this. Your box will crawl, kswapd will chew up a lot of the processor, Linux needs swap enabled, lets just hope its not used.
So how do you stop Nagios pages because of swap usage? Well if you have a few choices.
reboot the box
or
stop mysql && swapoff -a;swapon -a;
or just
swapoff -a;swapon -a;
(注意！如果你在MySQL正在使用Swap时执行，会把MySQL搞死，所以执行前一定要反复确认Swap没有被使用。)
Doing the latter command is rather scary and fun at the same time. Because you can either crash mysql or not. I just did the swap* commands live, I was very certain nothing was using swap and it worked. YAY no more pages and I didn’t have to shut down the service!
参考文章：
http://mysqldba.blogspot.com/2008/05/linux-64-bit-mysql-swap-and-memory.html