Home Discussions Questions & Answers SQL Performance Diagnosis: High I/O Wait Time

SQL Performance Diagnosis: High I/O Wait Time

Avatar photoCustomer June 19, 2024 at 5:51 pm

When using the DBA AWR SQL Performance Summary, which metric should I focus on to identify SQLs specifically bottlenecked by reading/writing data (I/O)?

Viewing 4 reply threads
  • Author
    Replies
    • Support June 20, 2024 at 6:25 am  

      Focus on the ‘User Io Wait Time’ column. This shows the total elapsed time in seconds from the wait event class ‘User I/O’.

    • Avatar photoCustomer June 22, 2024 at 5:26 am  

      The default sorting shows the most CPU-intensive SQLs first. If I want to prioritize tuning IO-bound queries or network issues, how should I sort the data?

    • Support June 24, 2024 at 3:33 am  

      If tuning server load is the goal, CPU is usually prioritized, but if you want to spot other bottlenecks like IO or network waits (e.g., ‘SQL*Net message from dblink’), you should sort the report by ‘elapsed time’ instead of CPU time.

    • Avatar photoCustomer June 25, 2024 at 10:47 pm  

      If I notice high IO, should I also investigate table modification tracking?

    • Support June 27, 2024 at 8:34 pm  

      Yes, tracking table modifications can be useful for performance context. You can use the DBA Table Modifications report to see the number of rows modified since the last analysis, provided table monitoring is active.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: