Measuring the impact of Redo Log change
- From: Deepak Sharma <sharmakdeep_oracle@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Mon, 8 Sep 2008 21:32:34 -0700 (PDT)
We recently (today) moved the redo logs from RAID5 to RAID1+0.
The obvious reason of doing this is to make things better in terms of
performance, as RAID1+0 is better suited for read/writes. Someone pls correct
me if that's not true.
What are different ways to measure the impact of this change?
The platform is AIX, DB is 10.2.0.3 and DB size is 55TB, and 2TB redo is
generated each day. There are plans underway to reduce the redo generation
using direct path etc. (so let's not get diverted by that).
We can try measuring the wait event stats using AWR, session stats etc., but
what exactly to look for? 'log file switch completion', 'log file sync', are
some things that come to mind - what else?
Thanks,
Deepak
Other related posts:
