DBAsupport.com Forums - Powered by vBulletin
Results 1 to 8 of 8

Thread: RAW vs Cooked file system

Threaded View

  1. #4
    Join Date
    Feb 2003
    Location
    Leeds, UK
    Posts
    367
    Hi Tamil

    The best throughput will be the lowest the denominator of disk controller through put and disk throughput. What is the maxmum number of physical reads that the disk subsystem achieved?
    According to the paper they "used Oracle and HP performance tools to collect statistics during the entire run for each test case. (They) compared the different run results using the application throughput measured in number of transactions per minute, the log_file_parallel_write, db_file_sequential_read, IO throughput and CPU utilization". The results for raw with and wiithout async were:

    Raw without async IO (medium and heavy workloads):

    TRANSACTION THROUGHPUT 23135 28168
    IO THROUGHPUT 3316 3898
    LOG_FILE_PARALLEL_WRITE 9 ms 9 ms
    DB_FILE_SEQUENTIAL_READ 9 ms 19 ms
    CPU UTILIZATION 80% 88%

    Raw with async IO (medium and heavy workloads)

    TRANSACTION THROUGHPUT 31961 35367
    IO THROUGHPUT 4877 5392
    LOG_FILE_PARALLEL_WRITE 4 ms 8 ms
    DB_FILE_SEQUENTIAL_READ 12 ms 26 ms
    CPU UTILIZATION 79% 91%

    So no actual stats for reads alone unfortunately

    [edited to tidy formatting]
    Last edited by hacketta1; 12-30-2004 at 06:40 AM.

Posting Permissions

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


Click Here to Expand Forum to Full Width