Overclocking Your Database Servers
It seems like I’ve been programming forever (we’re talking TS-1000, TRS-80, and Commodore64). I’ve always been looking to improve the performance of my programs, especially database applications. Better performance can usually be attributed to one of the following:
- New Hardware – [insert name of favorite hardware vendor] has just released new server technology that incorporates improved [RAM | CPU | Disk | RAID Controller]. At some point we’d purchase one of the new servers, install the OS and RDBMS software, restore a large database for benchmarking, and run scripts to test the performance. Performance always improved but it was never proportional to the time and money invested.
- New Database Version – [insert name of favorite database vendor] has just released version [insert version], now with [insert shiny new feature]. There are always “compelling” with each new release that “just might” improve the performance of your application. As with hardware, this usually improved performance marginally (though sometimes had no impact or decreased performance).
- Restructuring Data (tables/indexes) and/or Code (SQL) – I always found this to be the best way to dramatically improve performance. However, you eventually you reach the optimal design of data and code.
Break out your liquid cooling and lets see who can hit 200,000 TPS on a single-socket!
I’ll sneak into the marketing storage closet and find prizes for the fastest systems reported.