使用MONREPORT.DBSUMMARY工具对DB2 LUW性能急救

今天IDUG推送的文章头条，写的不错，周末一定把他翻译出来。

http://www.idug.org/p/bl/et/blogid=278&blogaid=625

Steve Rees, April 24, 2017

Investigating performance problems doesn’t have to be hard.  There are some basic steps you can take to find common bottlenecks in your system – ‘performance first aid’ if you will.  We’re going to look at some of these basic problems and how to find them, using just DB2’s built-in capabilities.

其实调查性能问题并不是很难，可以采用很多基本步骤来发现系统来的常见性能瓶颈 －来进行性能急救。我们现在就来看一看一些基本问题，以及我们是如何使用DB2的内在功能发现他们的。

Performance problems are almost always about time – how long something takes to run, or how many things (transactions, statements, etc.) can be done in a certain amount of time.  So, for most performance problems, we primarily want to understand where time is being spent.   This is a fundamental principle that applies not only to the basics that we discuss here, but also to more unusual issues you may run into from time to time.

性能问题大部分是关于时间的－ 运行某某花多长时间，或者在一段时间里，

Fortunately, DB2 has many effective ways to figure out where time is going.  The ‘mon_get’ monitor table functions and administrative views provide loads of helpful data about DB2 performance.  Because this is ‘first aid’ and not brain surgery, we’re going to go with the easiest, most ubiquitous tool – monreport.dbsummary.