Starting point should still be looking at where your database is waiting at, and how the waits relate to CPU usage. Then pick the biggest component (either CPU or a wait), and see how that can be decreased. frits On Tue, Apr 29, 2008 at 4:58 PM, Zhu,Chao <zhuchao@xxxxxxxxx> wrote: > We have some databases with load profile like lots of light query (mostly > pk based), each execution cost only 3-6 buffer_gets and no complex join > etc. > But due to excessive executions (10K+ query per second), load is also > driving pretty high. > > Anyone has experience tune such kind of application/database? From single > SQL point of view, they are already perfect. > > -- > Regards > Zhu Chao > www.cnoug.org >