Results 1 to 6 of 6

Thread: Raw or cooked?

  1. #1
    Join Date
    Jan 2004
    Location
    San Antonio, Texas
    Posts
    47

    Question Unanswered: Raw or cooked?

    Hi All,
    Has anyone actually seen performance gains with raw in DB2? When would you recommend it?

    HP/UX 11i 64-bit
    DB2 V8.1.4
    1.5 TB OLTP database with nightly batch proccesses.

    Thanks,
    DBAgirl

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1

    Re: Raw or cooked?

    Originally posted by DBAgirl
    Hi All,
    Has anyone actually seen performance gains with raw in DB2? When would you recommend it?

    HP/UX 11i 64-bit
    DB2 V8.1.4
    1.5 TB OLTP database with nightly batch proccesses.

    Thanks,
    DBAgirl
    There definitely is a performance advantage of raw devices (not files ) as opposed to SMS. However, if your disk subsystem is not the best then the file system caching of SMS can sometimes perform better than raw device access. It also depends on the configuration of your RAID (I guess you do have a RAID). Write performance of some RAIDs could be noticeably worse than that of JBODs.

  3. #3
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: Raw or cooked?

    If you have an advance storage system, like IBM Shark, to my experience, you may not see a big difference in performance between File and Raw DMS devices ...
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  4. #4
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Another consideration is whether there are a lot of table space scans or index space scans (which cause a lot of prefetch activity). Significant prefetch activity is the one area were raw "may" have a slight advantage.

    Significant amounts prefetch activity usually does not occur in an OLTP environment, so any slight theoretical benefits of raw over cooked will probably not be seen. Having decent sized buffer pools also helps keep the difference to a minimum.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  5. #5
    Join Date
    Jan 2004
    Location
    Egypt
    Posts
    61

    Re: Raw or cooked?

    Originally posted by DBAgirl
    Hi All,
    Has anyone actually seen performance gains with raw in DB2? When would you recommend it?

    HP/UX 11i 64-bit
    DB2 V8.1.4
    1.5 TB OLTP database with nightly batch proccesses.

    Thanks,
    DBAgirl

    there are many factors that affect DB2 I/O performance:

    1st is the Disk load balancing ( OS & paging space on physical disks, DB2 filesystems on other physical disks )

    2nd Access time of the logical partion of db2 filesystems ( under AIX you can assign allocation type Center/Outer/Core/Inner )
    try to use the Center part of the disk ( give minimum access time)

    3rd Buffer Pool size of the Database, as much as 70% of the machine memory should be allocated to the DB buffer pools ( in case that the machine is a native DB server )

    4th Type of Table Space ( SMS or DMS ) for unix systems DMS is much faster than DMS specially in large databases

    5th Wait I/O should not be more than 25% of the CPU usage, otherwise there shoud be a need for I/O tunning on the system
    Last edited by hanyheggy; 01-30-04 at 23:04.
    hany heggy,
    IBM certified Professional, AIX system support
    www.melodyhits.tv

  6. #6
    Join Date
    Mar 2003
    Posts
    343
    What if DMS filesystems are mounted using the DIO option? Would that narrow the gap between raw and cooked for a DSS system where prefetching does happen? Also is anyone using this option(DIO) and if so are there any concerns?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •