High Elapsed Time - with heavy I\O sync

Larry Kintisch

High Elapsed Time - with heavy I\O sync

January 23, 2008 04:57 PM

Hi Rao,

You have a classic bad index issue. Synchronous I/O takes from
100-times to 1000-times longer elapsed time and 10-times as much
CPU
as sequential access in the correct index. If you are in the
USA
please call me at home 845-353-0885 for some guidance.

In any case, part of the "Cost-Saving Index Design" 2-day class
that I teach [see: www.DBIndexDesign.com ] is also covered by
IBM
course CV960 [was CF961] and by the Redbook "SG24-7134-00 DB2 UDB
for
z/OS: Design Guidelines for High Performance and Availability"
that
you may download from:

The IDUG DB2-L Listserv is only part of your membership in IDUG.
DB2-L list archives, the FAQ, and delivery preferences are at
http://www.idug.org/lsidug under
the Listserv tab. While at the site, you can also access the IDUG
Online Learning Center, Tech Library and Code Place, see the latest
IDUG conference information, and much more. If you have not yet
signed up for Basic Membership in IDUG, available at no cost, click
on Member Services at http://www.idug.org/lsms