How to measure improvement after splitting tablespaces into multiple disk volumes? (Oracle 10g AWR) I have a recently released 10 000 user analytical application that is suffering from performance issues because of excessive amount of transactions. Apart from re writing many of the SQLs in the application for better performance we are also on top down approach where we are adding more volumes and tweeks to memory etc. An Oracle specialist redesigned our sever from single tablespace with 2 volumes to 2 tablespaces with 4 volumes where the indexes will have their own volume and tablespace. Each volume is a separate disk array so they do not compete for IO.

We have executed this change in development env and we are about to move into acceptance but before paying for the change the business would like to see measurable gains.

Where in the AWR report can I make comparisons to measure such data on the before and after the change is executed?
From user APC:

The AWR has this section called IO Stats. Not unreasonably, this is where it reports the statistics for IO activity. Within that section there are figures for each tablespace. You need to run these reports against the target database. Ideally you want several different runs, each run being no more than twenty minutes long; the longer the run, the more likely it is that the law of averages will drain meaning from the figures you get.

So, the principle is: you run this report and get a benchmark. Then you deploy your changes and re-run the report. The difference in the various columns is the performance benefit of the change. Really you would want to requests and data per sec go up, average time and waits go down.

To make these figure more convincing you should run the same workload in the before and after tests. This is where something like Real Application Testing really comes into its own.