In December 2009, I weighed about 210LBs. My wife was nagging me about losing weight. My blood pressure was a bit high and so was my resting heart rate. Adding insult to injury, I stepped on our new Wii Balance Board and our Wii Fit Plus game verified I was overweight. You can argue (unsuccessfully) with your wife, but you can't argue with a game. There was only one thing I could do. I started running my butt off. By April 2010, I weighed 180LBs and ran in my first 10K race. In September 2010, I ran in the Philadelphia Half Marathon. By the end of 2010, I logged just over 500 miles for the year. Last month, April 2011, I ran in the Nashville Half Marathon. I've had a lot of time to think about how tuning "me" is like tuning DB2... |
In December 2009, I weighed about 210LBs. My wife was nagging me about losing weight. My blood pressure was a bit high and so was my resting heart rate. Adding insult to injury, I stepped on our new Wii Balance Board and our Wii Fit Plus game verified I was overweight. You can argue (unsuccessfully) with your wife, but you can't argue with a game. There was only one thing I could do. I started running my butt off. By April 2010, I weighed 180LBs and ran in my first 10K race. In September 2010, I ran in the Philadelphia Half Marathon. By the end of 2010, I logged just over 500 miles for the year. Last month, April 2011, I ran in the Nashville Half Marathon. I've had a lot of time to think about how tuning "me" is like tuning DB2... |
For my age, height, and weight, my Nordic Track treadmill says I burn about 40 calories every quarter mile, or usually about 495 calories for a 5K (3.1 miles). Calorie burn rate varies a little according to your speed, but not much. If you walk a 5K, it'll likely take you 60-75 minutes, but you'll burn roughly the same number of calories as someone that runs the same distance in 15-30 minutes.
You need to burn about 3,000 calories to lose a pound (assuming consistent caloric intake). So, six 5K walks later you could be a pound lighter. Just START!
In the realm of DB2 tuning, we have the same challenge. There are performance fires to fight (DB2 server is having a heart attack), security to administrate, auditing to implement, utilities to run and check, and multiple projects clamoring for your time. Important projects miss target dates due to seemingly constant fire fighting. Proactive Tuning? Ha! There's no time for that!
Folks, you have to just START. Put a stake in the ground. Block off an hour or two each week on your calendars and START PROACTIVELY tuning your DB2 databases so that you can avoid the heart attacks and reduce the fire fighting. With each little bit of successful tuning that you achieve, the database becomes more efficient at processing work (transactions / queries). As the database loses excess weight and becomes increasingly more efficient, CPU utilization of the server will decrease. A healthier database can subsequently handle peak activity rates without performance deterioration or the need for fire fighting.
OK. Glad we got started! I'm already looking forward to Lesson #2 in Part 2 of "Running DB2 LUW Faster: Performance Lessons Learned on the Treadmill".
Questions? Comments? Feedback? Contact DBI.
Cheers,
Scott
PS - I am a DB2 doctor, but I'm not a health doctor. Consult your physician before beginning any exercise program. Consult with DBI before changing your hardware, applying fixpacks, or upgrading DB2.